Le 10/03/2025 à 19:36, Andrey Rakhmatullin a écrit :
Every stable Debian release only contains one Python version, normally
the newest one at the time when the release was made. Testing and
unstable can contain two versions during the transition from the older
one to the next one.
Clear
I just encountered recently a few venv that require 3.10 to work in at
least 2 ai stable diffusion software, really difficult to package
right now.
Not sure what do you mean by venv but for local use you aren't required
to use Python interpreters from the distribution and can e.g. use pyenv
to install any other one.
I mean that in many case projects suggest to do
python3 -m venv venv ; . venv/bin/activate
then :
- the pip upgrade
- pip install -r requirements_versions.txt
but as far as i understand, the virtualenv can only be with the python3
version available on the system
and many upstream have complex dependency that only work for 3.10 or
3.13 or ..
not that i want to encourage the use of virtualenv instead of packaging,
but it's often only way except heavier dockerizing, especially boring
with GPU
Worth of packaging it ?
It seems easy to simply download and build and use.
Simply providing a Python interpreter in Debian is not generally useful,
and integrating it with the packaged modules is a lot of work which is
also impossible for older Python versions. So no. You can package it
locally if you want and if you don't expect it to work with any packaged
modules.
The idea would have it only for the virtualenv usage, not to have all
packaged modules, none if possible
A googling on
'installing python3.10 in debian bookworm'
let me think, it's a bit current issue
It's indeed amazing that the usual criticism about only old libs
available i heard so many, plays in the other direction.
I was surprised that python3.10 compiling from upstream tarball was so
easy, but it's maybe i was lucky
Cheers
Christian
