Hi, This needs some additional clarification, I'm not entirely sure what's going to happen. If I now tinker around with sid, the case is following:
python3.8 does not install ensurepip, however it installs the venv module (which dh-virtualenv requires). However, command "python -m venv /tmp/foo" fails as expected, since ensurepip is missing. Now, python3.8-venv contains the ensurepip module. But to me it is very unclear if python3.8-venv is going to disappear? It also makes depending on these packages generally a lot more brittle: I'd rather depend on python3-venv than python3.8-venv. We are not depending on the /usr/bin/pyvenv binary, but executing the module with "python -m venv", so it does not matter if the python3-venv just drops the binary. Could you please clarify what is going to be removed, which packages are going to stay? On Thu, Sep 24, 2020 at 4:31 PM Jyrki Pulliainen <jy...@dywypi.org> wrote: > On Thu 24. Sep 2020 at 16.02, Matthias Klose <d...@debian.org> wrote: > >> On 9/24/20 9:51 AM, Jyrki Pulliainen wrote: >> >> > Thanks for the bug report. >> >> > >> >> > Is pyvenv included in 3.8 in sid now? Package repository still lists >> >> > python3-venv as an available package in Sid > > >> >> >> it's still there, but will be gone for bullseye. >> >> > Ok thanks for the clarification! > > Is it included by default in python3? I tried eyeballing experimental > packages but failed miserably there to figure it out > -- > - Jyrki > -- - Jyrki
