touch-packages team mailing list archive

[Donald Stufft <donald@xxxxxxxxx>]

FWIW I think that ``python -m venv`` is the easiest (only?) way to
reliably say that you want to create a virtual environment for *this*
particular Python. This is especially important when multiple versions
of Python that have venv start to be able to be installed (either via
the system repos, or via PPAs like deadsnakes). In particular, there is
an inprogress rewrite of virtualenv to use the venv module for isolation
that will essentially be doing ``python -m venv``.

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