Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1026247 > unrolled thread

Bug#970810: python3-venv is gone

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#970810: python3-venv is gone Jyrki Pulliainen <jyrki@dywypi.org> - 2020-09-24 10:00 +0200
    Bug#970810: python3-venv is gone Jyrki Pulliainen <jyrki@dywypi.org> - 2020-09-24 15:40 +0200
      Bug#970810: python3-venv is gone Vincent Bernat <bernat@debian.org> - 2020-10-22 11:40 +0200

#1026247 — Bug#970810: python3-venv is gone

[Multipart message — attachments visible in raw view] — view raw

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

On Wed 23. Sep 2020 at 19.36, Matthias Klose <doko@debian.org> wrote:

> Package: dh-virtualenv
>
> Version: 1.2.1-1
>
> Severity: serious
>
> Tags: sid bullseye
>
>
>
> This package depends or build-depends on python3-venv, which is gone
> upstream.
>
> Please remove or re-implement that usage.
>
> --
- Jyrki

[toc] | [next] | [standalone]

#1026284

[Multipart message — attachments visible in raw view] — view raw

On Thu 24. Sep 2020 at 16.02, Matthias Klose <doko@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

[toc] | [prev] | [next] | [standalone]

#1029566

 ❦  6 octobre 2020 12:32 +03, Jyrki Pulliainen:

> 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?

From my understanding, only the pyvenv command will disappear.

Doko, why is python3.x-venv a separate package? It seems `python3 -m
venv` doesn't work without the ensurepip module shipped in
`python3.x-venv`.

python3-venv package was useful to pull the dependencies to get a
working venv module. Can we either keep the python3-venv as a
metapackage for this purpose and integrate back the ensurepip module
(300 bytes) into libpython3.x-stdlib?

Thanks.
-- 
Use the good features of a language; avoid the bad ones.
            - The Elements of Programming Style (Kernighan & Plauger)

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web