On Wed, 21 Oct 2020 15:03:08 -0500 Ken Moffat via blfs-dev wrote: > On Wed, Oct 21, 2020 at 12:53:27PM -0500, Bruce Dubbs via blfs-dev wrote: > > On 10/21/20 12:06 PM, DJ Lucas via blfs-dev wrote: > > > On October 21, 2020 11:25:42 AM CDT, Bruce Dubbs via blfs-dev > > > <blfs-dev@lists.linuxfromscratch.org> wrote: > > > > Currently we have /usr/bin/python -> python2. Is it time to change > > > > that > > > > to python3? > > > > > The requirements are met at this point I think, only a handful of > > > packages left now. Anything using only python2, that depends on the link > > > will need patch/sed. > > > > I'll note that we have 56 references to python2 in the book right now. Some > > pages have a couple of references so that is a slight overcount. Checking > > all those pages will require a significant effort. > > > > If a package can use p2 or p3, we might want to remove the reference to p2. > > > > -- Bruce > > > > It is probably time to start looking at this. Unfortunately, I know > that my normal desktop builds all use gimp2 so I build python2 very > early in BLFS. Unfortunately, I can't schedule any time for > preparing to test this at the moment. > > Changing python to python3 will probably cause breakage in a few > obscure or barely-used packages for a few weeks (or months), so > arguably starting sooner will find more of them before our next > release. > > Meanwhile I'll mention that node-js v14 (which can use python3) will > move into LTS around the 27th of this month. I've been using v14 > for a while now, to show willing, but I'll also mention that trying > to update from a previous version to current on anything except a > fully up to date system can fail with what look like C++ scope > errors from g++ (e.g. on BLFS-10, although my experimental build > this month was fine). But since we mostly care about having > everything up to date, only a (perhaps intermittent) problem for > those of us who have not updated everything ;-) > > ĸen > -- > The people next door oppress me all night long. I tell them: I work > all day, a man's got to have some time to learn to play the tuba. > That's oppression, that is. [ Guards! Guards! ] > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page
I did this as recently as last week. I think you'll find that changing the /usr/bin/python symlink is actually easier than patching the packages that are using that symlink and discovering 2 when you want them to discover 3, which is why I went ahead with changing it. On my system I have only qtwebengine and scribus that are still requiring 2 and they discover it by themselves. (But I have Python explicitly disabled in quite a few places that the book, being more generally applicable, wouldn't.) I have only libxml2 that needed an explicit force to 3 and you also need libxml2-2.9.8-python3-unicode-errors.patch that I got from Arch. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
