You can have a look at the ChangeLog when 3.10 was pushed. Ignore the "Upgraded." within the kde/ section, as he also upgraded KDE at the same time. Pay attention to the "Rebuilt." and that will give you a good idea of what packages need to be recompiled. It's basically anything with a python module, since those are all version dependent.

Below is the list of "Rebuilt." packages on that day. This list might not be all the packages as some were upgraded and some of these might've been rebuilt for something unrelated to the python bump, but as I said, it will give you a good idea of what packages might be in that list of 100ish packages (there's 112 here).

Here's the buildlist I used along with make_world.sh (like this in the slackware64-current/source directory):

reinstall python3.9 use venv
 

This is ridiculous, the world is moving to 3.10, there is no stopping that. You are correcting a mistake with another mistake.
You can just reinstall version 3.9 and use python virtual environment for those that do not build with 3.10

Wael Hammoudeh

Nobody, except Fedora, has moved to python 3.10 ...

well in Gentoo python 3.9 is still the default.
https://www.gentoo.org/support/news-...python3-9.html

Not even wild and crazy Arch Linux has it, not even in Testing (which means no immediate plans to upgrade it, if it's not there by this time).

Slackware is trying to stabilize for a release, python 3.10 was inappropriate at this stage of the game. There should be nothing that breaks things getting added to the distro at this time.

virtual environments? I would rather have appropriate system python versions installed so I don't have to resort to such tomfoolery. So I can just install things to site or dist. Right now that's python 2.7 and 3.9.

I totally agree that adding 3.10 was premature. Had I been asked BEFORE the addition, my answer would have been not now.
Now it was already added, I voted to keep it, I still do hold this opinion. When I say the whole world is moving to 3.10, I am not concerned with other distribution here, all python code is going to be ported to 3.10 and soon.

I've written a quick howto I added python 3.9 to current. It sure can be done in more elegant way -- find that here.
Python virtual environment is nothing new, I recall a howto by AlienBob from years ago for it, somebody can look that up; if you need to!
My opinion does not matter and I am not going to argue with anybody, the decision has been made. What is the point? I still can say it is the wrong decision.

I would like to see Slackware 15.0 released ASAP. I think PVE is a faster way toward that goal. This is another set back!

Wael Hammoudeh

I really would like python to be slotted like in Gentoo, you can have python 3.8, 3.9 3.10 and 3.11 alfa in the same system if you like and choose what python interpreter to use.
Instead of usr/lib64/libpython3.10.so and usr/lib64/libpython3.so like in Slackware, they have in Gentoo
usr/lib64/libpython3.10.so
usr/lib64/libpython3.10.so.1.0
usr/lib64/libpython3.9.so
usr/lib64/libpython3.9.so.1.0


I know in a source distro having python is slotted way is more useful than in a binary distro like Slackware but still would be a nice feature to have for someone who like to test stuff or build its own packages.

How will this effect programs built with 3.9? Is there anything that builds with 3.10 but not 3.9?

Hello all;

The decision to go back to 3.9 has already been made. It was not mine, and I am not trying to change it - I know that I can not. I am just voicing my opinion which I think I just did, maybe I should have spoken sooner!? But again I am not looking for an argument about my opinion, some people will agree with me and some will not. Unfortunately all this does not matter.

I am late to work, got to go, you will not hear from me for a while. Mr. volkerdi please release Slackware 15.0 ASAP.

Have a great day;
Wael Hammoudeh

Well now that those updates have arrived. I have decided it just not worth the effort to separately try to maintain separate Slackware packages for Python 3.10; just to many of them. So... hi ho, hi, ho, it's back to Python 3.9 for me.

Oh man after all the work upgrading all my packages to 3.10, this downgrade really sucks haha
I hope it goes back to 3.10 really soon, don't feel like rebuilding all my packages again...

I'm just catching up. I would have almost missed the downgrade to python3.9. A heads-up at the beginning of the changelog would be more sensible.

And curiously, you post exactly in the thread where PV made the announcement

Well it was identified
That said, I agree.

I've been following this thread, was well aware of this and waiting for it to appear in ChangeLog.txt There probably should have been a note at the top of ChangeLog.txt. The quote @marav posted would have been sufficient. One can maybe assume outside of the obvious "py", "python" packages everything "Rebuilt" was against python 3.9; however there are a few "Upgraded" in there too that need python. Any way my preferred mirror hasn't picked up the changes yet, so I wait until after the next cron job tomorrow. To start dealing with this and the real gotcha in that ChangeLog.txt

My video driver is NVIDIA 390.144, patched for 5.14.x, guess I find out tomorrow if it builds with 5.15.x. ;)