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.
Cairo ships with sphinx document building tool. Sphinx-build requires sphinx Python modules.
Without sphinx Python module:
Code:
root@darkstar:~/pkgs# sphinx-build
Traceback (most recent call last):
File "/usr/bin/sphinx-build", line 5, in <module>
from sphinx.cmd.build import main
ModuleNotFoundError: No module named 'sphinx'
root@darkstar:~/pkgs# _
Installing via pip adds quite a few dependencies (those available on Slackware -current were manually marked with an asterisk):
Worth to add all these extra Python modules to fix an included command, or leave it alone for users to install manually?
For context, bind-9.17.18 is building manual pages using sphinx, so it may turn into a future requirement whenever next stable 9.18 gets out, if not backported to the current 9.16 tree.
Cairo ships with sphinx document building tool. Sphinx-build requires sphinx Python modules.
...
Worth to add all these extra Python modules to fix an included command, or leave it alone for users to install manually?
For context, bind-9.17.18 is building manual pages using sphinx, so it may turn into a future requirement whenever next stable 9.18 gets out, if not backported to the current 9.16 tree.
Building kernel documentation also uses Sphinx. To build kernel docs I install Sphinx, sphinx-rtd-theme, and graphviz (and all dependencies) from SBo. I don't mind installing all that extra stuff from SBo just to build the docs.
Sun Oct 10 00:11:13 UTC 2021
A new Python (and related rebuilds), the latest release of the KDE Gear
applications, and a new kernel. Enjoy! :-)
I didn't expect such a big change in a release candidate. Patrick, where do you take us?
I guess Patrick meant well, so that Slackware 15.0 will not be released with an "outdated" python version. However, IMHO, he made a bad move since there are some (or many) applications that do not support python 3.10 yet (see https://wiki.qt.io/Qt_for_Python, for example), or do not work properly with it (like spyder-ide, for e.g.).
Even if things in the Slackware main tree is building/working fine, 3rdparty stuff should take a while to get back working properly.
So, I request to revert python3 to 3.9, since it will be supported until 2025, and wait until the next development cycle to include a later python version.
I guess Patrick meant well, so that Slackware 15.0 will not be released with an "outdated" python version. However, IMHO, he made a bad move since there are some (or many) applications that do not support python 3.10 yet (see https://wiki.qt.io/Qt_for_Python, for example), or do not work properly with it (like spyder-ide, for e.g.).
Even if things in the Slackware main tree is building/working fine, 3rdparty stuff should take a while to get back working properly.
So, I request to revert python3 to 3.9, since it will be supported until 2025, and wait until the next development cycle to include a later python version.
Best regards
NO , we have arround 2 months , for final release , we are only in rc1 , next rc2 ..some weeks to test.
Imagine revert python3 , and put python2 only cause some things not go updated to work under python3.
NO , we have arround 2 months , for final release , we are only in rc1 , next rc2 ..some weeks to test.
Imagine revert python3 , and put python2 only cause some things not go updated to work under python3.
I don't really have an opinion on this, because I'm not impacted, but from what Fellype said, he never talked about a revert python3 --> python2
but rather python 3.10 --> python 3.9
Anyway, I highly doubt this will happen
Generally speaking, and this is more the fault of Mr. Volkerding who gives bad habits to everyone because of the stability of what he proposes,
slackware-current is not a stable version and it is advised not to use it in a production environment or similar
When Slackware 15.0 is officially released, many projects will be updated to support Python 3.10, so i guess it's just a matter of time. Nothing to be afraid of
The boost package still contains references to python 3.9, eg. /usr/lib64/libboost_python39.so.1.77.0; it probably needs a rebuild.
The slackbuild needs a trivial patch to support python 3.10:
NO , we have arround 2 months , for final release , we are only in rc1 , next rc2 ..some weeks to test.
Imagine revert python3 , and put python2 only cause some things not go updated to work under python3.
I haven't asked for python2
Quote:
Originally Posted by marav
I don't really have an opinion on this, because I'm not impacted, but from what Fellype said, he never talked about a revert python3 --> python2
but rather python 3.10 --> python 3.9
Anyway, I highly doubt this will happen
I also doubt it will happen. But it costs nothing for me to request. Furthermore, my comment was intended to provide feedback from what I have been observing on the python world - in addition to what Didier commented.
Quote:
Generally speaking, and this is more the fault of Mr. Volkerding who gives bad habits to everyone because of the stability of what he proposes,
slackware-current is not a stable version and it is advised not to use it in a production environment or similar
Yeah, I know that. However, as said Didier, Slackware 14.2 is getting old. And I believe this is the reason why some users moved from 14.2 to -current. Specially those that need Qt5 and python3.
Quote:
Originally Posted by willysr
When Slackware 15.0 is officially released, many projects will be updated to support Python 3.10, so i guess it's just a matter of time. Nothing to be afraid of
Yeah, of course it's just a matter of time. Some projects, like numpy, started supporting python 3.10 when it was at a rc stage. But others will take too long to do that. Of course, this is not a problem with Python, nor with Slackware for having adopted the .0 release.
I guess Patrick meant well, so that Slackware 15.0 will not be released with an "outdated" python version. However, IMHO, he made a bad move since there are some (or many) applications that do not support python 3.10 yet (see https://wiki.qt.io/Qt_for_Python, for example), or do not work properly with it (like spyder-ide, for e.g.).
Best regards
Well, that explains what happened to Frescobaldi. Game-breaker for me, but I finally set up atom to do lilypond and supercollider, so win, ultimately? If you code, I recommend atom.
But, yeah, things break with current. It's way more stable than most "rolling" releases, but these things happen, too, especially after big updates.
The boost package still contains references to python 3.9, eg. /usr/lib64/libboost_python39.so.1.77.0; it probably needs a rebuild.
The slackbuild needs a trivial patch to support python 3.10:
As per usual, I've had to raid Alien Bob's site for what I regard as essentials,
Libreoffice
vlc
Multilib
Wine
qbittorrent
cabextract
chromium-ungoogled - (firefox has sold it's soul)
ffmpeg
and there's always more gathered during the life of an install, which is about 6 months (Thanks Alien).
and it's a pity slackware doesn't include them as well, because there's often version issues with libraries.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.