On Jan 28, 2015, at 12:46 PM, Stratos Moros wrote: >I haven't looked into newer Ubuntu versions, so everything I'm posting >is about Trusty. > >As far as I can tell, virtualenv's bundled pip wheel is not built by >Debian maintainers, but by virtualenv's developers themselves.
You're right, Trusty does it differently. This is in fact the reason why virtualenv in Trusty works, but pyvenv doesn't. The bundling of the wheel files violates Debian policy. This was discovered for pyvenv and disabled before it was fixed properly. The proper fix (made in the Debian first) didn't make it into Ubuntu until after Trusty. virtualenv *also* violated Debian policy but that wasn't discovered until later, so the policy-violating-but-working version of virtualenv is present in Trusty. Later, in Debian (and you'll find all these tools fixed in Jessie) we fixed both virtualenv and pyvenv to be compliant with Debian policy *and* actually work. ;) Unfortunately Trusty didn't get any of these fixes. I've talked to many many people about this and I think it's a real problem. Ideally, and especially because Trusty is an LTS, we would fix both virtualenv and pyvenv to be both policy-compliant and working. That would certainly be in the best interest of our users. The difficulty is because there's a stack of packages that would need SRUing to do it properly; not just virtualenv and Python 3.4, but also the 6 or so dependencies which all build the .whl files that virtualenv and pyvenv vendor (in upstream). We'd also need to pull the python-wheel package into Trusty since it didn't appear in Debian until after Trusty was released. Needless to say, this is a complex problem with a proper solution requiring a significant amount of resources to accomplish. That's assuming that such SRUs would be approved in the first place. I'll try to at least have some conversations with the appropriate people to figure out whether and how we can fix this for Trusty. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415028 Title: virtualenv's included pip does not use system libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-virtualenv/+bug/1415028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs