Well that's just dandy. It is what it is I guess. I'm not happy about it. I've got everything I use working with Python 3.10. Wish I could keep Python 3.10 installed, but that's an exercise in futility unless I want to recompile all of the dependencies in Slackware. Maybe blacklisting those packages will work or moving them in to my repository and adding a tag. I just finished compiling Mozilla Firefox 94.0 using the source tree; had to use the latest version of nodejs (16.13.0) in build-deps because that version in their wanted 3.9; typing this in 94.0.

Oh well.:banghead:

I intend to the same thing, keep 3.10 and blacklist 3.9. I'm not sure why that is a problem?

It's one thing to blacklist packages you don't use, another if you are using them. Blacklist removes them from the picture.

Since I use slackpkg with slackpkg+, if I do this, I plan to take all of those packages and put them in my repository and add my tag to them so I can tell the difference between my packages (They are mine now, since they are no longer part of the tree.) and Slackware's (no tag). I will also add the source build to my repositories build. I do this now for three Slackware packages, cups, imagemagick, and mozilla-firefox.

I might just suck it up and rebuild all my stuff back to python 3.9 too.

I think this basically sums up how I feel about the whole thing. This release on current has gone so long that I feel like even Pat has done slight things to be respectful towards users on Current who might not otherwise be on current.... but in the end current still is the development branch... I don't think a 3 week test on the next python release is bad, all and all.

As Eric has pointed out in a reply on his blog, it's possible (although there are a few caveats) to have Python3-3.9 and -3.10 installed alongside each other:
https://alien.slackbook.org/blog/pac...#comment-43512

This might be a convenient option for those who have rebuilt a lot of 3rd party packages.

IIRC I only had to rebuild a few and I've kept the old packages, so I'll probably go back to them after the regress to 3.9.

There were valid arguments for both choices. Portraying it as "cooler heads" vs (implied) "hot heads" is an unfair characterisation of the situation.

IMO there was no right choices here, just two sub-optimal ones: Slackware was just a victim of timing on this one.

Agree. One does not have to like it, to accept it. It's part of being a tester. All users of -current are, like it or not.

Yes I understand why this decision was made. I sighed when 3.10 was tossed in the mix. After a few days, I just accepted that python 3.10 as gonna happen and acted accordingly.

Oh well, the decision has been made to fall back to 3.9, so be it. I will deal with it.

Slackware is still be best damn operating system on the planet. That is my opinion and I am sticking to it.

Like it.

Agree.

You are welcome and I agree, lets do this.

PV took Slackware and his "eco-system" as a whole.
What do people like Ponce for SBo, Eric Hameleers for all the packages he provides, and Didier Spaier with Slint are invaluable for lot of people, and for me. They are alone to do what they do and they deserve respect for their contribution to the Slackware "eco-system", that is what has been done by PV.

Do they do jokes on this forum?

What hundred python3 packages are there in Sackware? Do they all need to know what version of python3 is on the box (i.e. use python3.9 specific code instead of api)? It all comes down that they get directed where python3 is. After the change only the folder with site-packages (your own third-party stuff) remains in /usr/lib64/python3.9 or /usr/lib/python3.10.
'
I probably move straight to the next 'current'; would 'stable' not be a joke anyway with all the ongoing kernel-updates? (well, that's a joke ;-)

Poor choice of phrase. My intended point was less dramatic.

Well, I do not know precisely.

BUT, I remember precisely that our BDFL said that he needs to rebuild over 100 packages from -current to switch back or fort with those Python versions.

So, shipping an alternate Python3.10 on /testing will mean to ship along also those over 100 packages on /testing.

Did you imagine the Slackware 15.0 being released with over 100 various packages on /testing ? I for one, NOT.

I think your choice of phrase was accurate. There was a lot of toxic behavior on the part of people who don't have any stake in the discussion. Many of them made it very clear that they don't even care yet they felt compelled to give their opinion. If the version of python you use doesn't matter, why get involved?

Personally, I did not appreciate the whole "IT IS TESTING SO SHUT UP" attitude from a handful of people here. One of the great things about Slackware is that everyone gets an opinion, but that opinion isn't guaranteed to be accepted in the final release.

Ultimately the people who shouldn't have a say, didn't get a say! :)

Toxic behavior? Who commenting in this thread does not have a stake in the discussion. Name one person who said it is "testing so shut up".

Hmmm, so it would make it impossible to remain with python3.10 unless those 100 or more upgrades coming our way need to be ignored? Maybe good to know which ones these are. If KDE-based than it would be managable at my end (no KDE on this box) and no need to switch back. If not KDE, then the slog of rebuilding my numerous python-packages has to be taken up....

https://www.linuxquestions.org/quest...ml#post6292044