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.
Oh, I can imagine Python 2 being kept around as a legacy technology for a while. Like SDL1, GTK1, GTK2 and QT4.
.. and jdk6! There's still a lot of mission-critical corporate infrastructure out there which breaks under jdk7, so companies keep jvm6 going on their servers.
The python folks are really pushing to "deprecate" py2, but I expect it will remain in use for a decade or more.
Or maybe start transitioning to a /usr/bin/python2 and /usr/bin/python3 programs with a symlink for /usr/bin/python -> /usr/bin/python2. Then you could run all python scripts using python2 to help the possible full transition to python3 (I have no idea how likely it is to completely switch to python3 way down the line).
Probably as an initial include of python3 would mean IMHO firstly how much slackware stuff can be run on py3. Then decide what is
better to do if use the python symlink or just leave py2 as default and py3 as an option. AFAIK most py3 stuff is programmed with
/usr/bin/python3 in the first line.
Probably as an initial include of python3 would mean IMHO firstly how much slackware stuff can be run on py3. Then decide what is
better to do if use the python symlink or just leave py2 as default and py3 as an option. AFAIK most py3 stuff is programmed with
/usr/bin/python3 in the first line.
I'm pretty sure I read that the shebang is based on how the installer was called. So, if you use /usr/bin/python2 setup.py install, it would have #!/usr/bin/python2 as the shebang at the top of the script.
I'm pretty sure I read that the shebang is based on how the installer was called. So, if you use /usr/bin/python2 setup.py install, it would have #!/usr/bin/python2 as the shebang at the top of the script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
)
