Skip to content

pip goes into infinite recursion due to recent commit #983

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
eteq opened this issue Jun 7, 2013 · 2 comments
Closed

pip goes into infinite recursion due to recent commit #983

eteq opened this issue Jun 7, 2013 · 2 comments
Labels
auto-locked Outdated issues that have been locked by automation

Comments

@eteq
Copy link

eteq commented Jun 7, 2013

A package I work on (which uses the developer pip for wheels support) recently started failing, and I tracked the problem to a recent pip commit. If you look at https://travis-ci.org/eteq/astropy/jobs/7866383 you'll see a perfectly successful build. However, if you look at https://travis-ci.org/eteq/astropy/jobs/7866415 you'll see that the same build fails in pip with a complaint about infinite recursion. The only difference between these two is that the one that works is using the pip from be0c47f, while the failing one uses 8344fb8 . This clearly demonstrates that 8344fb8 is at fault, although I have no idea how.

Just ask if you want me to try anymore debugging!

@dstufft
Copy link
Member

dstufft commented Jun 7, 2013

So this was a little interesting, the problem was that sourceforge has urls like http://sourceforge.net/projects/docutils/files/docutils/0.8.1/docutils-0.8.1.tar.gz/download which pip doesn't see as possibly non HTML so it doesn't bother doing a HEAD request and checking the content type. After we pass that check (without checking) pip just blindly assumes that the content it's getting is HTML and thus parseable.

So the fix was to, after we've fetched the url, inspect the headers and verify the content type.

@eteq
Copy link
Author

eteq commented Jun 7, 2013

Tricky - I guess the fact that it was erroring due to recursion was sort of a red herring then. Anyway, thanks for the quick fix!

@lock lock bot added the auto-locked Outdated issues that have been locked by automation label Jun 6, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Jun 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
auto-locked Outdated issues that have been locked by automation
Projects
None yet
Development

No branches or pull requests

2 participants