[SOLVED] What version of Python 3.x should ship with Slackware 15.0?
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.
View Poll Results: Which python3 should ship in Slackware 15.0?
Please let it be Python 3.10, whenever 15.0 ever comes out (if ever). There is no point in deprecating Python when everyone else is going forward. The packages will catch up soon enough. Also, please stop wasting everyone's time making special slackware python packages when anyone can "pip install <python package>". Same goes for perl, ruby, ... There are already people managing these packages. You don't have to do it yet again. And those who are interested can install python 2.7 or 3.9, nothing is stopping them.
Also, please stop wasting everyone's time making special slackware python packages when anyone can "pip install <python package>". Same goes for perl, ruby, ... There are already people managing these packages. You don't have to do it yet again. And those who are interested can install python 2.7 or 3.9, nothing is stopping them.
I do not want to use pip for Python installs. I want a Slackware package for that. I do not use Perl's cpan either.
They are wasting their time and ours. Instead of this distraction they could concentrate on getting a Slackware release every year instead of 5 years and counting. Too bad if you don't want to use pip or cpan or cpanm or pear or ... What do you do if you need to install a python package that is not in slackware or slackbuilds?
Last time I looked into it these package repos had little in the way of code auditing, and lacked basic must have security measures like cryptographic signing.
You may be ok with that, but unless they get these basic security measures in place, it's a hard pass from me and I suspect many others here.
I build the python packages "manually", however pip comes handy at least to provide information about packages, like list the installed ones and show information about them or find missing dependencies. I also use "pip --user install" as an easy way to find dependencies of a new module I want to package.
I build the python packages "manually", however pip comes handy at least to provide information about packages, like list the installed ones and show information about them or find missing dependencies. I also use "pip --user install" as an easy way to find dependencies of a new module I want to package.
I like this idea. Gonna have to read up a bit more on pip.
To analyze first the content , then you can makepkg from the personal directory you send , for easy and clean uninstall , like original packaged things.
When i talk to overwrite files , thats occurs when a new version requires new module , one example is some things want sip6 and we have version 4 , you can later encounter a conflict , then probably netter way is see more old version to pair and no overwrite sip , or whatever.
Last edited by USUARIONUEVO; 10-18-2021 at 09:43 AM.
To analyze first the content , then you can makepkg from the personal directory you send , for easy and clean uninstall , like original packaged things.
When i talk to overwrite files , thats occurs when a new version requires new module , one example is some things want sip6 and we have version 4 , you can later encounter a conflict , then probably netter way is see more old version to pair and no overwrite sip , or whatever.
Thanks. I learned the hard way about pip (and cpan) a while back. This is one reason I prefer to create my own packages. I also think packages (to me at least) are the Slackware way of installing things. Packages are simple to keep track of and as you mentioned above, good for a clean install. I already have done some reading. I'm looking at list, show and check commands as possibly useful. You can bet any testing I do with be on a test system. I do most of my dependency checking at build time, there always seems to be one extra not mentioned.
Large packages like spyder, a Python IDE, have many python package dependencies. So your choice is:
$ pip install spyder
or
$ [manage and create 130 python slackbuild install packages and install them (and maintain them every time there an update)]
Enjoy! ;-)
I'll take the second choice, thanks. More control over what is installed. A for the 130 packages, well some are optional, some I already have installed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
