registry team mailing list archive

[termie <launchpad@xxxxxxxxxxxxxx>]

I am late to this thread but I don't think this issue is valid.

I don't understand how you are getting the error you are getting. Either
you are using a clean virtualenv and the only version of anyjson
available for download is 0.2.4 or you are not using a clean virtualenv.

In the first case it means we should change the pip-requires file to be
more lenient on the version of anyjson, in fact we don't even require it
some other library does.

In the second case we just need to make sure we are passing the right
flags to make a clean virtual env.

Towards the patch that already appears "Merged" the exact opposite patch
to change the behavior form doing what you are already doing is how we
got to this point, so that patch should be reverted pending discussion
with the people who reviewed and discussed the original patch (i think
myself, monty and soren). The main goal was not to install anything on
anybody's system without them agreeing to it first, and additionally any
packages that need to be installed globally probably need to be run with
root so the script should choke if it tried to install virtualenv
without being run with sudo.

As for installing pip in the virtualenv itself that seems fine, though I
don't feel like it has much impact.

As for checking the build stuff for m2crypto I don't think there is much
of a way around telling them it is somewhat tricky, but we can certainly
check if they are linux and if they are check with apt-get and tell them
what to do, `uname` is usually enough to determine their platform or we
can `which` apt-get

-- 
pip-requires and virtualenv don't play together nicely
https://bugs.launchpad.net/bugs/615906
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack.