SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Firefox is dependent on Python2 to compile from source? That's pretty crazy actually. Anyways, I was searching the web trying to find a list of "relevant" packages which still use python2, but I could find nothing. So your example is interesting (and shocking).
I'm not shocked that someone doesn't want to retool their complex build environment. There's a half assed attempt to provide a python2 environment by including an obj-x86_64-pc-linux-gnu directory populated with a Python 2.7 environment but that's the wrong thing to do, and I have yet to see it actually work. It fails my build for me if I don't nuke that directory first.
In my one and only time and horrible experience with Python, that was NOT the case. It does not seem to work as expected under all circumstances, that's my experience at least. I didn't know Python well, so I might have done something wrong, but I tried a variety of things when installing Python 3, and the Python 3 based libs, software and extensions etc refused to install to Python 3 paths etc properly and/or do/work as expected. I even switched python from python2 to python3 and it did me little good.
Here a bunch applications are linked to Python3, others to Python2 with no issue. Indeed Pyhon2 and Python3 are installed side by side and coexist peacefully.
Code:
didier[~]$ ls -l /usr/bin/python*
lrwxrwxrwx 1 root root 9 avril 29 02:14 /usr/bin/python -> python2.7
lrwxrwxrwx 1 root root 14 avril 29 02:14 /usr/bin/python-config -> python2-config
lrwxrwxrwx 1 root root 9 avril 29 02:14 /usr/bin/python2 -> python2.7
lrwxrwxrwx 1 root root 16 avril 29 02:14 /usr/bin/python2-config -> python2.7-config
-rwxr-xr-x 1 root root 6200 mars 3 21:11 /usr/bin/python2.7
-rwxr-xr-x 1 root root 1681 mars 3 21:10 /usr/bin/python2.7-config
lrwxrwxrwx 1 root root 9 avril 29 02:14 /usr/bin/python3 -> python3.5
lrwxrwxrwx 1 root root 16 avril 29 02:14 /usr/bin/python3-config -> python3.5-config
-rwxr-xr-x 2 root root 10336 août 30 2017 /usr/bin/python3.5
lrwxrwxrwx 1 root root 17 avril 29 02:14 /usr/bin/python3.5-config -> python3.5m-config
-rwxr-xr-x 2 root root 10336 août 30 2017 /usr/bin/python3.5m
-rwxr-xr-x 1 root root 3079 août 30 2017 /usr/bin/python3.5m-config
didier[~]$
I think , at least python , need points to python3 instead 2... like archlinux are doing since 1 year or more...to start python2 deprecation is the first pass to do.
slackbuilds can provide python2.
As i say , i think the first and probably more hard pass, is make python3 , the default , cause need to make changes in too many slackbuilds...but is the start point for this ... in some moment that is happen.
wicd needs python2 , and is a excellent option , for people not networkmanager fans or problems with it.
but again , i think slackbuilds can adopt, but not sure if not better option make in /pasture , cause some times issues with network , can make imposible to build wicd from slackbuilds, cause no conection.I think this is important point to see.
Last edited by USUARIONUEVO; 08-26-2019 at 05:45 PM.
I was talking about your experiences with Python, not your issues with Fedora (I have no idea about that).
Oops, my bad. I don't think it was actually. I just found Python a horrible environment to work with. It's been awhile, but I can try to remember the reasons that I was thinking so if you care. One of the things was pip and actually basing a script on a web address being fetched correctly. I think one thing I was trying to do was to insert some kind of tiny lib or function into python, but I was not allowed to do that without pip, even though I had it at hand. Sure, that was a user error, but I just found the method disagreeable. I had the same experience trying to install something else to python as well.
It's not fresh in my mind, but some of those scripts were horrible and ugly with things I never wanted to know existed.
I think I even wrote down a sarcastic list about that experience somewhere after I was dealing with it.
As i say , i think the first and probably more hard pass, is make python3 , the default , cause need to make changes in too many slackbuilds...but is the start point for this ... in some moment that is happen.
//snip
Making python3 the default Python interpreter is like making c++ the default C compiler. Cool, but crazy.
Most of it has, but of particular concern are sbo packages and the software that ships with Slackware.
I see, but considering the "end of life January 2020", do they not HAVE to adapt?
I hate to put a burden on you here, but can you give any examples of "core" software that Slackware is likely to use which is still on Python2? Sorry for being such a pain about this, but I'm just trying to understand the situation more indepth.
I see, but considering the "end of life January 2020", do they not HAVE to adapt?
That Python2 be considered EOL doesn't mean that software relying on it will cease to work overnight. And to be adapted these software will need someone to work on it. Including this one that I maintain
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
