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.
Sometimes i think people not understand , but write.
python development team , says bye bye python2 , in 2020 , then thinking in large slackware development cycles , we need to do something arround , cause launch slackware 15 in ..middle of 2020 ? , with python2 is not good idea.
In /pasture , ok , if someone want then here is , but as default package i think NO , comparing c/c++ with python2/3 is a very bad comparison cause c/c++ are part of same package (gcc) , and never need to put one of this as a default cause executables are differents and no defaults needing.
This is the same like python/python2 , in some moment all migrate to python2 ... now is time to go with python3 , and the first pass , is make as default python executable version 3.
Its a hard work , cause need first of all , make changes in very large slackbuilds scripts, build , to see if some package fails , and test later , question here is when edit slackbuilds ...mantain python2 in , or out.
Last edited by USUARIONUEVO; 08-27-2019 at 03:38 PM.
I just want to point out that Slackware still ships gtk+-1.2.10. Just because the upstream drops support does not mean the program is instantly broken.
I just want to point out that Slackware still ships gtk+-1.2.10. Just because the upstream drops support does not mean the program is instantly broken.
gtk1 is in slackware ONLY , for xmms , i request some time update to xmms2 to drop gtk1 , or simply remove xmms , i think slackware stock , provide too many media players , mplayer/xine is the only nedded , but have audacious, kplayer , xmms amarok , amp , dragon ....
Last edited by USUARIONUEVO; 08-27-2019 at 04:30 PM.
I use XMMS occasionally. It's an easy and quick way to play a mp3 file. Quodlibet is my go to music player because of its media organization. I feel the same regarding xine and mplayer but I prefer QMPlay2 for its CUDA support and media organization.
I think it depends if Pat thinks python2 is worth the effort to keep around. I know a lot of stuff has moved to python3 but maybe python2 is worth keeping around a bit longer. Then again python2 could be removed and put on slackbuilds.org like python3 is now for 14.2.
I just want to point out that Slackware still ships gtk+-1.2.10. Just because the upstream drops support does not mean the program is instantly broken.
It does mean that whatever security holes were present when upstream drops support will still be there.
People have had 10 years to update their python 2.x.x code to python 3.x.x. It's like the Y2K bug all over again.
Sometimes i think people not understand , but write.
python development team , says bye bye python2 , in 2020 , then thinking in large slackware development cycles , we need to do something arround , cause launch slackware 15 in ..middle of 2020 ? , with python2 is not good idea.
In /pasture , ok , if someone want then here is , but as default package i think NO , comparing c/c++ with python2/3 is a very bad comparison cause c/c++ are part of same package (gcc) , and never need to put one of this as a default cause executables are differents and no defaults needing.
This is the same like python/python2 , in some moment all migrate to python2 ... now is time to go with python3 , and the first pass , is make as default python executable version 3.
Its a hard work , cause need first of all , make changes in very large slackbuilds scripts, build , to see if some package fails , and test later , question here is when edit slackbuilds ...mantain python2 in , or out.
Who mandated that cc and c++ be in the same package? Slackware didn't follow this convention, at least.
If you have time to update all the scripts around the world from the past decades, then please do it. If you mean your little casual use-and-drop scripts, that's for your own distribution. Probably open another forum.
We dropped IDL exactly because it only allows purchasing license of the latest version, and scripts written for old versions then become incompatible, causing us to re-write scripts from last N years in year N+1.
Python is marginally better, and will be much better if we keep python2 as python2 and python3 as python3.
It does mean that whatever security holes were present when upstream drops support will still be there.
People have had 10 years to update their python 2.x.x code to python 3.x.x. It's like the Y2K bug all over again.
People have 20 years to update their c89 code to c99, and I didn't see anyone blaming c89 style, nor did any reasonable cc drop the support. There are still code bases in c89 that are actively maintained.
Making python3 the default Python interpreter is like making c++ the default C compiler. Cool, but crazy.
You say THIS , and im say IS NOT THE SAME , cause gcc have separate names for diferent executables and NEVER CONFLICTING , python without number execute a one version as default ...points to python2 or python3 executable.
If you no understand that simply example, please no write more.
Like others in this thread i go add you at ignored , cause i start think your trolling.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.