> 1) Treat the .whl files in ensurepip as data files, or alternatively bundled > copies > of code that are intended to be bundled (as per the Debian manual in > 4.13), > and continue to do your normal modifications to python-pip.
chapter 4 talks about source packages, not binary packages. And these have to be rebuilt from source. At least the windows installer binaries don't have any source code. > 2) Don't debundle things from python-pip (thus making you have to maintain > a second set of patches against anything bundled) and rewheel into the > venv. That would mean, using another copy of the pip & friends sources, and having different pip versions on the system. 3) Leave ensurepip broken and make myself and lots of Python developers sad ;( Sure. 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1290847 Title: pyvenv fails due to mising ensurepip module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
