Hi, Is there a technical reason why maintaining multiple versions of Python on debian is not possible? I understand that it would be an engineering effort but I am curious if there is more fundamental reason that makes having multiple versions of Python on debian difficult.
Thanks, Caleb On Tue, Jan 26, 2021, 3:39 AM Matthias Klose <d...@debian.org> wrote: > On 1/14/21 4:13 PM, Urs Schroffenegger wrote: > > * What outcome did you expect instead? > > > > a virtual environment to be created. > > > > > > Furthermore, I can run previously created virtualenv using python3.8, > but I > > can't install packages with pip, also with missing distutils errors. > > > > I don't know if this is a bug or if it's to be expected on unstable. But > it > > seems to me that python version numbers started to change faster lately. > What's > > debian's policy for other versions of python than the latests ? If older > > version have no support, is there a debian way to work with multiple > versions? > > Or should I use something like pyenv for those cases? > > Debian ships with one Python3 version only. So once we are finished with > upgrading to a new Python version, the old Python3 version (3.8 in this > case) is > removed. The removal bug https://bugs.debian.org/978710 is not yet > addressed. > > Note that you also find snapshot builds for 3.10 in experimental, but > there's no > support for any third party modules. > > If you want to maintain packages for 3.8 yourself, you have to provide the > binary packages built from the source packages python3.8 and > python3-stdlib-extensions yourself. > > Yes, Python3 upstream now has a planned twelve months release cadence. > > Closing this issue as won't fix. > > Matthias > > -- > To unsubscribe, send mail to 980106-unsubscr...@bugs.debian.org. >
