@ambv One of the symptoms of installing multiple #Python versions on my #Ubuntu #Linux system is dependency errors. I have installed your #Python312 interpreter, which is unable to be configured (the other #Deadsnakes installations have succeeded).

I just released #Python 3.11.7 on #deadsnakes, and Anthony Sottile released 3.12.1 and 3.13.0a2.

Yeah, from now on, I'll be helping him get the releases out as part of the regular CPython release process.

https://github.com/deadsnakes/python3.11/actions/runs/7145158923

.github/workflows/main.yml Β· deadsnakes/python3.11@d530e80

Contribute to deadsnakes/python3.11 development by creating an account on GitHub.

GitHub

@dplattsf

You can generally safely use the "deadsnakes" ppa/repo to install alternate Pythons, even though they're primarily an Ubuntu thing.

One caution, which bit me when #Debian 12 was released - before doing a major Debian upgrade that bumps the default Python to one you have installed from #deadsnakes, remove the deadsnakes version first. I got ... interesting breakage that took me a bit to figure out the right fix for.

But there's also AppImages... https://github.com/niess/python-appimage/releases

Releases Β· niess/python-appimage

AppImage distributions of Python. Contribute to niess/python-appimage development by creating an account on GitHub.

GitHub

#Debian #major #releases come along so rarely I always forget something since the last time I upgraded.

#Bullseye -> #Bookworm this time, and that was fun πŸ˜‚

#Lesson learned; perhaps this will save someone else some time.

If you have #Python 3.11 installed on Bullseye from the "#deadsnakes" ppa, uninstall it before attempting the upgrade. It conflicts with the Python 3.11 package in Bookworm in a way that causes the upgrade to #fail partway through. Then you have to manually fix it all...