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


Groups > linux.debian.bugs.rc > #286679 > unrolled thread

Bug#970810: python3-venv is gone

Started byMatthias Klose <doko@debian.org>
First post2020-09-23 18:40 +0200
Last post2020-10-22 23:00 +0200
Articles 5 — 3 participants

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


Contents

  Bug#970810: python3-venv is gone Matthias Klose <doko@debian.org> - 2020-09-23 18:40 +0200
    Bug#970810: python3-venv is gone Jyrki Pulliainen <jyrki@dywypi.org> - 2020-10-06 11:40 +0200
      Bug#970810: python3-venv is gone Jyrki Pulliainen <jyrki@dywypi.org> - 2020-10-13 20:10 +0200
    Bug#970810: python3-venv is gone Jyrki Pulliainen <jyrki@dywypi.org> - 2020-10-22 13:40 +0200
    Bug#970810: marked as done (python3-venv is gone) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-10-22 23:00 +0200

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

FromMatthias Klose <doko@debian.org>
Date2020-09-23 18:40 +0200
SubjectBug#970810: python3-venv is gone
Message-ID<ASfYd-a2-1@gated-at.bofh.it>
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.

[toc] | [next] | [standalone]


#287451

FromJyrki Pulliainen <jyrki@dywypi.org>
Date2020-10-06 11:40 +0200
Message-ID<AWRBT-7Ys-3@gated-at.bofh.it>
In reply to#286679

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

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 <jyrki@dywypi.org> wrote:

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


-- 
- Jyrki

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


#287693

FromJyrki Pulliainen <jyrki@dywypi.org>
Date2020-10-13 20:10 +0200
Message-ID<AZwUh-1Dz-3@gated-at.bofh.it>
In reply to#287451

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

Hello,

A week to removal and I’m still looking for clarification to this issue

On Tue 6. Oct 2020 at 12.32, Jyrki Pulliainen <jyrki@dywypi.org> wrote:

> 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 <jyrki@dywypi.org> wrote:
>
>> 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
>>
>
>
> --
> - Jyrki
>
-- 
- Jyrki

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


#288207

FromJyrki Pulliainen <jyrki@dywypi.org>
Date2020-10-22 13:40 +0200
Message-ID<B2H6N-1Tz-1@gated-at.bofh.it>
In reply to#286679

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

On Thu, Oct 22, 2020 at 12:37 PM Vincent Bernat <bernat@debian.org> wrote:

>  ❦  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.
>

Hi all,

I added a package to mentors that addresses the issue, albeit in a somewhat
ugly way. Available here
https://mentors.debian.net/debian/pool/main/d/dh-virtualenv/dh-virtualenv_1.2.2-1.dsc

The change in question is doing some trickery in the debian/rules file on
figuring out which Python version we are running at build time (which can
probably backfire in some cases), and would indeed want that metapackage
instead :)

- Jyrki

-- 
- Jyrki

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


#288232 — Bug#970810: marked as done (python3-venv is gone)

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2020-10-22 23:00 +0200
SubjectBug#970810: marked as done (python3-venv is gone)
Message-ID<B2PQL-6ZD-17@gated-at.bofh.it>
In reply to#286679

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

Your message dated Thu, 22 Oct 2020 20:48:44 +0000
with message-id <E1kVhVs-0009X4-I8@fasolo.debian.org>
and subject line Bug#970810: fixed in dh-virtualenv 1.2.2-1
has caused the Debian Bug report #970810,
regarding python3-venv is gone
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
970810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970810
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


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


csiph-web