consider this requirements file
and know that:
what you end up with in site-packages is metadata for both being installed:
Pygments-1.4-py2.6.egg-info (whats in the req file)
Pygments-1.5-py2.6.egg-info (the latest)
Pygments is not considered the same as "pygments".
this does not happen, when the requirements file is this:
I've also seen cases like this with "Django", where Django is installed with a url link, and some other requirement depends on "django"
the diff here is very small, and I added a test, which required some new packages. the fix amounts to closing a loophole in the way 'unnamed' requirements were being added to the requirement set. they were bypassing the method that adds the lower case alias.
upper case url reqs should be recognized as same as other lower case …
comments on 'unnamed' requirements