On December 12, 2019 11:30:59 PM CST, Ken Moffat via blfs-dev <blfs-dev@lists.linuxfromscratch.org> wrote:
> >Going forward, perhaps we need to install python3 as both python3 >and python, and find a way to stop python2, if it is installed, >installing as python ? > >Maybe as simple as: > >1. in LFS ln -sv python3 /usr/bin/python > >2. in BLFS, if installign python2 : > rm /usr/bin/python > ln -sv python3 /usr/bin/python > > ?? > >Yes, I know that upstream python has claimed that python should >still be python2, but I think we're fast going to reach the point >where that causes more trouble than it is worth. That's not exactly correct. We are at the point where the majority use python3. We need to get rid of python2 build instructions for remaining modules that are not dependencies for something else using python2, sed/patch the remaining packages to explicitly use '/usr/bin/python2' or '/usr/bin/env python2' and then we are compliant with the PEP (84 IIRC) with a python->python3 symlink. The big thing is the "majority" of packages, though it was worded differently IIRC. Arch can really help here. > >For the moment, I'm giving up on this slithering mess. > >Maybe I'll try creating the python symlink, or maybe it would be >easier to just start banging my head agaisnt a brick wall. > --DJ -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
