I sent a message to the list a while back about a modification to the
build scripts for python3 stuff that allowed the same script to be used
for any version of python you wanted. It didn't make it so the packages
was certain to build, rather it let you specify on the command line
which version of the interpreter to use and if the build completed
successfully it put a tag in the finished package name to indicate which
version it was for, the default being 3.9. There didn't seem to be much
interest though. I can send you a copy of the script I wrote to convert
an existing script if you want it.
What I do is I have a folder called archive where I put all the packages
after they are built. In there I made folders for each python version I use:
./archive
./archive/python3.9
./archive/python3.14
./archive/src
the src subdir is for the modified source ( I bundle the source code in
as well), then if I need a package built for a version I just set the
environment variable, unpack the source tar, build and install. Had to
do a stack recently and have some ideas on ways to automate the process
(I don't like pip) but haven't done it.
The reason I mention it is that with that approach there is no
duplication of upstream packages. Only downstream packages have
different names. Not sure about setup.py based packages but
pypackage.toml based stuff I know includes the minimum version of python
which could be included in the SBo listing easily enough I think.
Any way if you want it I can send the conversion script.
On 1/2/26 08:01, Eugen Wissner wrote:
I have a Pyhton 3.12 SlackBuild:
https://git.caraus.tech/OSS/slackbuilds/src/branch/master/python3.12
I tried to submit it recently to SBo and my submission was rejected, because it
would result in even move duplications in Python packages, so python2-packages,
python3-packages, python3.12-packages. Maybe it would be possible to make all
Python 3 packages depend on a newer Python 3 version provided by SBo and not by
core Slackware.
There was a similar attempt to submit newer ruby version.
But, yeah, we’re not living in the world where programming languages are stable.
Am 02.01.2026 um 02:06 schrieb Glenn <[email protected]>:
Actually it is not rich it is the latest version of markdown-it-py
(https://slackbuilds.org/repository/15.0/python/python3-markdown-it-py/?search=markdown_it)
that doesn't support 3.9 anymore. Rich uses markdown-it-py which is where that
came from.
On 1/1/26 12:38, Glenn wrote:
A number of python packages I have looked at recently have dropped support for
python 3.9, e.g. rich 4.0.0 What is the policy regarding providing an upgraded
package provided by Slackware? I know in the past I have seen newer versions of
Qt on SBo. I installed python 3.14 quite awhile ago. It lives happily next to
3.9. I just modified the Slackware script but I could get it into, I think, the
right form for submission here. If it wouldn't pass though I don't want to
spend the time to do it.
Part of my reason for asking is that I am working a project that I think would be of use
here but it uses 3.14 so it wouldn't work under "stock" 15.0. Another
consideration is that the current version listed in slackware-current/d is 3.12, but that
may well be upgraded before the next release.
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
