[Bug 1290847] Re: pyvenv fails due to mising ensurepip module

[Barry Warsaw]

On Apr 24, 2014, at 07:38 PM, Matthias Klose wrote:

>So why not build the wheel files from the Debian python-pip source
>package, build-depending on python-six, python-requests, etc, then
>revert the de-vendorize patch.  The binary package should have Built-
>Using information about these build dependencies.   Then provide exactly
>this wheel in the python-pip and the python3-pip packages.

I think we'll have to basically build the recursive vendorized pip from
scratch, using the build-depend packages.  We'll probably have to write some
scripts to put all that together, which will include reversing the
de-vendorizing patches, recursively.

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

Title:
  pyvenv fails due to mising ensurepip module

Status in “python3-defaults” package in Ubuntu:
  Confirmed
Status in “python3.4” package in Ubuntu:
  Confirmed
Status in “python3.4” package in Debian:
  New

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