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

[btreecat]

Matthias Klose, coming from a distro who does a lot less mucking about
with upstream packages, having deafult language behavior broken infavor
of idealistic guidlines is just plain bad for UX.

Spin it how you want to but shiping broken packages means some one just
means someone spent the time trying to make the package conform (and I
agree with Ivo, why is this just now an issue when virtualenv was
shipping "incorrectly" before.) but failed to take the time to make it
actually work as expected. It happens, but it should not happen when it
does not need to. This was clearly an idealistic need rather than
technical need. Thats why I say "needlessly."

Barry Warsaw, thank you for the bump. Too often some one says they will
fix it only to let it languish.

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