If I'm reading the rewheel code correctly, I think we are going to have to do something like the following:
* Package up wheel for Debian (python-wheel, and python3-wheel). This gives us the setuptools bdist_wheel command. * At Python build-time we need *.dist-info/RECORD files for setuptools, pip, and recursively vendored packages. We do not currently generate these, and there's a bit of a bootstrapping problem. But let's say for the moment we can generate all these dist-info directories, we need to put them some place where the python3.4 debian/rules can find it *without* downloading anything from PyPI. My thought is that we bootstrap this by building setuptools-wheel, pip-wheel, etc binary packages which only contain the dist-info/ directories. We can then build-dep python3.4 on those *-wheel packages. * We need to package up rewheel too, both in PyPI and Debian. It'll take a little work to whip the code in shape, but it's not too bad I guess. I really don't like patching Python the way rewheel does it, so I'll look at alternatives. Hopefully bkadrda will accept pull requests. Anyway, that's a general plan, and the devil is in the details, but I think I see how it all hangs together. -- 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
