-
Notifications
You must be signed in to change notification settings - Fork 185
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New Release with Python3.11 Support? #355
Comments
my 2¢: If I understand correctly, Debian testing is also affected and the problem makes dh-virtualenv useless for all users?! That would justify a bugreport with severity |
Currently Debian Bookworm ships Python 3.10, I guess they will not bump it to 3.11 before the freeze, right? So when Debian Trixie becomes Testing, that will be affected. |
The default Python in Debian bookworm is now 3.11: https://tracker.debian.org/news/1414484/python3-defaults-3111-1-migrated-to-testing/ |
I'm also affected by this problem. Our build depend on dh-virtualenv and it's fail on Bookworm with the following error:
Seams related to the fact Bookworm is now using Python3.11 by default. |
For the record: in Debian's dh-virtualenv 1.2.2-1.3 the patch from #354 was cherry-picked as NMU. A dh-virtualenv release including this would still be nice. |
Does it mean dh-virtualenv should work in Debian Bookworm ? |
Yes: https://packages.debian.org/bookworm/dh-virtualenv (changelog). Works for me. |
Please consider cutting a new release, several fixes on the master branch did not make it into distro packages yet (like for example enabling --verbose with --builtin-venv). |
#354 added Python3.11 support for dh-virtualenv. Since Debian sid currently ships its python3 package in version 3.11.1-1, the currently released dh-virtualenv version 1.2.2 does not work.
I saw that @nailor is also the Debian maintainer for dh-virtualenv, it would be best to have a new release and a corresponding Debian package version. I could alternatively send a backport of the patch in #354 as a Debian bug report.
What do you think?
The text was updated successfully, but these errors were encountered: