[Feature] Python2 on Debian Bookworm

[puneearyan]

Hi,

I am working on Debian Bookworm to validate GPU features using Wayland 10. i have more number of Python2 scripts to execute the test case. Unfortunately Python2 support is completely dropped in Debian Bookworm.

Is there a way to get Python2 support on Debian Bookworm like adding ppa repository in the multistrap.conf.

Thanks,

[sunrat]

Bookworm is Testing so moved to Testing and Unstable subforum.

[Dai_trying]

Is there a way to get Python2 support on Debian Bookworm like adding ppa repository in the multistrap.conf.

Although this doesn't answer you question my approach would be to convert the scripts to Python3 in order to save more work (and workarounds) in the future...

[puneearyan]

Thanks @Dai_trying for your quick response.

Indeed, we also have plans to upgrade Python 2 scripts to Python 3. In the mean time, I simply wanted to experiment with adding Python2 support to Bookworm for quick verification.. Was curious to know if it is possible.

Anyway thanks for the update.

[abu_bua]

For the sake of simplicity I would use anaconda.

[sunrat]

For the sake of simplicity I would use anaconda.

Please explain how that would help the OP with Python2, considering the page you linked says anaconda is Python 3.9.

[waymao]

Regarding anaconda, you will need to install python3 and download some variant of anaconda. Mini Forge would be one distribution of conda.
Then you may run

Code: Select all

conda create -n <environment name> python=2

and python2 will be installed for the environment chosen.

[fadedbee]

I have installed Python 2.7 in Debian 12 (Bookworm) using Debian 11 (Bullseye) packages:

Installing Python 2.7 on Debian 12 (Bookworm)

[sunrat]

Note that installing packages from foreign releases is not supported officially and is classed as creating a Frankendebian.
Of course it may work fine but if it doesn't you are on your own. Python 2 was sunsetted 4 years ago - https://www.python.org/doc/sunset-python-2/

[fadedbee]

Thanks for the warning, I have added it to my blog post. Does this only become a practical issue if Debian 12 adds packages whose files clash with those provided by these specific Debian 11 packages? Or there other things to watch out for? (I doubt that Debian will add packages for python 2.7, libffi7 or libssl1.1 in future.)