Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Kitterman <debian@kitterman.com>
Newsgroups: linux.debian.maint.python
Subject: Re: MBF for deprecating Python2 usage
Date: Fri, 04 Aug 2017 05:30:01 +0200
Message-ID: <uaBtf-1rM-9@gated-at.bofh.it>
References: <uawjU-5YP-3@gated-at.bofh.it> <uazhM-8iN-19@gated-at.bofh.it>
Old-Return-Path: <debian@kitterman.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Approved: robomod@news.nic.it
Lines: 53
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:9687

Dropped d-devel=2E

On August 3, 2017 9:08:10 PM EDT, barry@debian=2Eorg wrote:
>On Aug 3, 2017, at 17:57, Matthias Klose <doko@debian=2Eorg> wrote:
>>=20
>> While at DebCamp, Stefano Rivera and I sat down to analyze what needs
>to be done
>> to deprecate Python2 usage within the distribution=2E  It might not be
>possible to
>> drop Python2 for the next release, but there are still too many
>issues with
>> packages=2E  For now we identified some categories which need fixing=2E
>These are
>> documented at https://wiki=2Edebian=2Eorg/Sprints/2017/Python3Montreal,
>resulting in
>> more than 3000 bug reports=2E  That's a high number, on the other hand
>we won't
>> make much progress if the issues are not named=2E  My intent is to
>bring that up
>> in the Python BoF next week at DebConf and then filing these bug
>reports with
>> the user tags mentiond on the wiki page=2E
>
>Great to hear that you guys talked about it=2E
>
>Just a quick note that PEP 394 discussions have revived, lead by the
>Fedora folks=2E  Please do check out the new thread, especially if you
>have opinions about what /usr/bin/python should do once Python 2=2E7 is
>EOL=2E
>
>https://mail=2Epython=2Eorg/pipermail/linux-sig/2017-August/thread=2Ehtml
>
>Cheers,
>-Barry

Read it=2E  I remain completely convinced that /usr/bin/python pointing at=
 a python3 version is utterly wrong and a disservice to our users=2E  Even =
after we remove python2=2E7, people will be locally compiling it and using =
it for a decade=2E

Such a change would be actively user hostile=2E

When python2=2E7 goes away, /usr/bin/python should go too=2E

Before python2=2E7 goes away, any python3 scripts/apps need to work with /=
usr/bin/python3=2E  Making them work with /usr/bin/python too doesn't actua=
lly help anything=2E  All it does is look pretty for us old timers=2E

I've said before and I've yet to see anything to cause me to have any doub=
t on the matter, that as long as I am one of the python-defaults maintainer=
s, /usr/bin/python will not point at a python3 version=2E

Scott K