touch-packages team mailing list archive

[Dario Bertini <berdario@xxxxxxxxx>]

@rspeer @wolfgang-richter

The bug is "sort of fixed"

You have to install python3-venv, this will make the ensurepip module
available, and the creation of a virtualenv will succeed

Imho this is an horrible naming choice: the error you'll get when trying
to run `python3 -m venv` mentions ensurepip, and most ubuntu/debian
users might have heard about the fact that ensurepip is disabled in the
distro

then, `apt list ensurepip` or `apt search ensurepip` won't yield any
useful results (just like I tried to do, before being puzzled about the
"fix released" status of this bug)

moreover, `--without-pip` will just work even without the new package,
making the name "python3-venv" even more misleading

Still, I'd caution you AGAINST using venv... I just found another
trivial bug. You're better off using virtualenv, given how it's battle
tested

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1290847

Title:
  pyvenv fails due to mising ensurepip module

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions