touch-packages team mailing list archive

[Launchpad Bug Tracker <1365728@xxxxxxxxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1348954 ***
    https://bugs.launchpad.net/bugs/1348954

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: python3.4 (Ubuntu)
       Status: New => Confirmed

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

Title:
  SRU: pyvenv fails due to mising ensurepip module

Status in python3.4 package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * Anyone attempting to use the pyenv script from Python 3.4 will be
  met with a fairly confusing error by default. This would have worked
  fine in saucy and raring.

   * While this can be worked around by adding a flag to the pyvenv
  script, it also removes the ability to have pip installed into a
  pyvenv virtualenv at all. This will prevent people from using one of
  the new features that comes with Python 3.4.

   * This should be backported to the stable release because it is a
  major regression in Python 3's pyvenv from previous Ubuntu releases.
  Additionally it removes one of the documented features of Python 3.4.

  [Test Case]

   * This can be reproduced just by doing ``python3.4 -m venv
  /any/tmp/path``. You will get an error that says something like:

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

  [Regression Potential]

   * I believe that the primary risk for regression will be within the
  python(3)-pip packages. This is because the patches that fixed this
  changed the build process there. I do not however believe that there
  will be any subtle or non obvious regressions (if any at all).

  [Other Info]

   * The original bug for this can be found at
  https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1290847

   * This regression comes from the fact that in Python 3.4 an additonal
  module was added to the stdlib, called ensurepip, that shipped a
  binary package (a Wheel) of pip. This allowed Python to include a
  command (python -m ensurepip) which would bootstrap an installation of
  pip into the current environment. The venv module was then modified to
  use this to install a copy of pip into the new virtual environment.
  The Python package was patched to rm -rf the ensurepip module during
  the install breaking the venv module in the process.

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