[Python-Dev] Another update for PEP 394 -- The "python" Command on Unix-Like Systems
chris.barker at noaa.gov
Wed Feb 13 18:31:10 EST 2019
On Wed, Feb 13, 2019 at 12:29 PM Barry Warsaw <barry at python.org> wrote:
> I think we should aspire for this to be the case too, eventually. When
> this has come up in the past, we’ve said that it’s not appropriate to
> change PEP 394 until Python 2 is officially deprecated. OTOH, I appreciate
> that distros and others have to make decisions on this now. I think it’s
> worth discussing where we eventually want to be as a community, even if we
> continue to recommend no official change until 2020.
I don't think end-users will see any discontinuity in 2020. For quite a
while now, more and more people have shifted from using python2 as the
default to using python3 as the default. On the other hand, some folks are
still using python2, and will continue to do so after 2020 (old, still
supported versions RedHat anyone?) Hopefully, after 2020 no one will start
anything new with py2, but it's going to be around for a long, long time.
So as there will be no time for a "clear break", we might as well make
changes when the time "seems" right. And has been pointed out in this
thread, there are a lot of folks not following the PEP anyway (virtual
environments, conda, ??). I myself have been telling my newbie students to
make a link from "python" to python3 for a couple years (before I saw that
I personally would like for `python` to be the latest Python 3 version (or
> perhaps Brett’s launcher), `python2` to be Python 2.7 where installed (and
> not mandatory). `python3` would be an alias for the latest Python 3.
Christopher Barker, Ph.D.
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker at noaa.gov
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-Dev