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
Network failure leads to TypeError in retry #742
Comments
Hmm, yeah, this is less than ideal. How does |
I can really only see one flow where this might happen at the moment, which is if Oh! But maybe it isn't! I think this isn't strictly a urllib3 bug, it's a requests/pip bug. Are your tracebacks complete, @JohannesBuchner, or did you trim them? |
I used pip3.4; I did not trim the traceback. |
Hmm. It feels like parts of the traceback are missing, but I guess they only go as far back as they got unwound to. Regardless, let me ask this: where did you install pip from? |
I've definitely seen this before. That said, this traceback is interesting. urllib3 is vendored into requests, but requests isn't vendored into pip. Very weird. Also, pip passes its own Retry object iirc. Let me go digging. |
Gentoo repos. I used pip to install a local egg directory, which loaded some dependencies off the web (sqlalchemy to be precise) |
So pip creates its own Retry object. cachecontrol is involved in this traceback though.
I wonder if there's a bug in the version of cachecontrol that gentoo has packaged. |
It's possible, but my concern is more that if pip/requests is providing a Retry object, that because of the shenanigans in kennethreitz/requests#2870, the |
I have CacheControl version 0.11.5 |
@Lukasa from the traceback it would appear gentoo is not unvendoring urllib3. That bug shouldn't be the cause here. |
So sounds like this is a pip/requests bug? (Feel free to re-open if I'm mistaken.) |
I got this traceback after a network failure with urllib3 v1.10 on Linux:
The text was updated successfully, but these errors were encountered: