Re: PEP 394

2018-10-21 Thread eryk sun
On 10/20/18, Terry Reedy wrote: > > On Windows, there is a better solution: the py launcher. > > py # launches the most most recent version installed* > > py -x # launches the most recent x.y > > py -x.y # launches x.y if installed, else lists installed versions > > * At first, 2.x took

Re: Re: PEP 394

2018-10-20 Thread Chris Angelico
On Sun, Oct 21, 2018 at 12:41 PM Peter via Python-list wrote: > > I'd imagine the PEP would stay as active, but changed so that: > > python2 -> always refers to python v2 > python3 -> always refers to python v3 > python -> which currently refers to python v2 will change to point to > python v3 Th

Re: Re: PEP 394

2018-10-20 Thread Peter via Python-list
at, 20 Oct 2018 12:57:45 +1100 Ben Finney skrev: Anders Wegge Keller writes: Short and simple: Do you expect PEP 394 to change status The status of PEP 394 today is “Active”. What change of status would you expect in this Informational PEP? One possible change would be that it would becom

Re: PEP 394

2018-10-20 Thread Terry Reedy
On 10/19/2018 3:03 AM, Anders Wegge Keller wrote: Short and simple: Do you expect PEP 394 to change status or recommendation when official support for Python2 ends in 13½ months time, or at least some time thereafter? For those that don't have the habit of memorizing PEPs, 394 is th

Re: PEP 394

2018-10-20 Thread Anders Wegge Keller
På Sat, 20 Oct 2018 12:57:45 +1100 Ben Finney skrev: > Anders Wegge Keller writes: > > > Short and simple: Do you expect PEP 394 to change status > > The status of PEP 394 today is “Active”. What change of status would you > expect in this Informational PEP? One pos

Re: PEP 394

2018-10-19 Thread Ben Finney
Anders Wegge Keller writes: > Short and simple: Do you expect PEP 394 to change status The status of PEP 394 today is “Active”. What change of status would you expect in this Informational PEP? > or recommendation when official support for Python2 ends in 13½ months > time, or at l

Re: PEP 394

2018-10-19 Thread Thomas Jollans
On 19/10/2018 18:38, Marko Rauhamaa wrote: > Thomas Jollans : > >> On 2018-10-19 12:06, Marko Rauhamaa wrote: >>> Anders Wegge Keller : * python3 will refer to some version of Python 3.x. >>> >>> Untrue for macOS, ArchLinux, RHEL and CentOS. >> >> Sure it's true for *EL (it's just that python

Re: PEP 394

2018-10-19 Thread Marko Rauhamaa
Thomas Jollans : > On 2018-10-19 12:06, Marko Rauhamaa wrote: >> Anders Wegge Keller : >>> * python3 will refer to some version of Python 3.x. >> >> Untrue for macOS, ArchLinux, RHEL and CentOS. > > Sure it's true for *EL (it's just that python3 might not be installed by > default even on EL7) T

Re: PEP 394

2018-10-19 Thread Thomas Jollans
On 2018-10-19 12:06, Marko Rauhamaa wrote: > Anders Wegge Keller : >> * python2 will refer to some version of Python 2.x. > > Untrue for macOS. > >> * python3 will refer to some version of Python 3.x. > > Untrue for macOS, ArchLinux, RHEL and CentOS. Sure it's true for *EL (it's just that pytho

Re: PEP 394

2018-10-19 Thread Alexandre Brault
the time being, all distributions should ensure that python, if >> installed, refers to the same target as python2, unless the user >> deliberately overrides this or a virtual environment is active. > Should, would, could. > Some platforms not being 394-compliant doesn't chang

Re: PEP 394

2018-10-19 Thread Marko Rauhamaa
Anders Wegge Keller : > * python2 will refer to some version of Python 2.x. Untrue for macOS. > * python3 will refer to some version of Python 3.x. Untrue for macOS, ArchLinux, RHEL and CentOS. > * for the time being, all distributions should ensure that python, if > installed, refers to the sa

PEP 394

2018-10-19 Thread Anders Wegge Keller
Short and simple: Do you expect PEP 394 to change status or recommendation when official support for Python2 ends in 13½ months time, or at least some time thereafter? For those that don't have the habit of memorizing PEPs, 394 is the one stating * python2 will refer to some version of P