On Wed, Apr 17, 2019 at 9:36 AM Jeff Smith <[email protected]> wrote:
> On Wed, Apr 17, 2019 at 9:22 AM Richard Melville via lfs-dev < > [email protected]> wrote: > >> On Tue, 16 Apr 2019 at 18:55, Jeremy Huntwork via lfs-dev < >> [email protected]> wrote: >> >>> On Tue, Apr 16, 2019 at 9:38 AM DJ Lucas via lfs-dev >>> <[email protected]> wrote: >>> > >>> > No, Arch links python->Python3 which the developers say explicitly not >>> to do. Don't do that. That is one of my long-standing complaints about >>> Arch. :-) >>> >>> Do you have a link to that recommendation? I'm interested in >>> understanding upstream's thinking on that. >>> >> >> I would be interested in seeing that link too, because as far as I was >> aware Guido, before he stepped down, maintained that Python *was* Python3. >> > > I was thinking the closest thing to an official position would be PEP-394: > https://www.python.org/dev/peps/pep-0394/ > Basically it says, in light of what Arch does and that Python 2 will > eventually be phased out, that for now applications should call on... > 'python' only if compatible with Python 2 AND 3 > 'python2' if compatible only with Python 2 > 'python3' if compatible only with Python 3 > For the distribution side of things, it states "for 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." - Jeff
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
