I don't know if there's a better way to do this, but I'm continuing where @dstufft left off over in #453.
I've tried to address the concerns raised in the original (hardcoded paths and other test issues).
I'm a little puzzled as to why the tests failed so spectacularly in python 3, but I started with replacing the iteritems() and the errors all seemed to go away. Here's a Travis CI build: http://travis-ci.org/#!/tgecho/pip/builds/1061109
The two test failures in 2.7/3.1/3.2 are for bundling, but I can't quite wrap my head around them yet. If someone with a better clue about pip internals could take a stab we'd be grateful.
There's another error in test_editable_git_upgrade in 2.5/2.6 that I'm not sure is related, but I'm looking at that. I'll also try to get a test on 2.4.
add the url we downloaded from to the InstallRequirement, and then re…
…cord it in info.ini
record the requirements line used to cause this package to install
make requirement_line the line that was passed to it and add support …
refactor handling of the info.ini file into a method that is passed a…
add tests to test info.ini on different types of installs
change the name from info.ini to pip.ini
use the available methods to get the egg info dir
Merge branch 'refs/heads/develop' into feature/record-download-info
Cleaned up info_file tests based on discussion in pypa/pip#453
Add branch to travis ci
Consolidated some of the testing code.
Remove iteritems() for py3 compatibility.
this addition should not be part of the pull request
Don't worry about Python 2.4 testing, we've bumped the minimum supported version to 2.5 for the next pip release.
I'm seeing the two bundle failures as well (and not seeing them in develop branch), I'll try to take a look soon and see if I can figure out what's going on with those.
Hmm I'm pretty sure I've seen those failures with the tests cache sporadically when running locally - it's possible we have a non-hermetic test which doesn't clean up after itself and this CL changes the ordering causing the failure.
@dstufft , this is fairly old. still important? if it is, can you explain what scenario is for this? I guess just to fill in the history of how that package got there? something more to give people in pip show?
I'm going to close this, the use case I had in mind is one I no longer thing is actually a good idea.