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
don't pin requests to a specific broken version #51
Comments
That's a httpretty requirement 2.8.1 so we need it to run tests. |
I looked in HTTPretty to figure out if they can fix it there, and they have a requirements.txt file that says:
so.... where is requests==2.8.1 required? :-) |
See development.txt file Would really appreciate if you could make httpretty work on Python 2 and 3 with later request! |
@tmylk not sure I understand. Why are we pulling in httpretty's |
An error is generated by httpretty when it is used with requests later version. |
@piskvorky
|
Apologies, I have incorrectly assumed you were asking for a later version of requests, but now I realise you wanted to use an older one. This is relaxed and merged in in #57. If you could report back if it fixes the issue for you that would be greatly appreciated. |
Requests are no longer pinned. |
Was there a reason to pin requests==2.8.1 instead of the much friendlier "<=2.8.1"?
That version of requests pulls in a broken version of urllib3 that cannot do SSL properly, so we have had to pin "requests<=2.7.0". Since you pinned to that specific version of requests, I have to also say:
If you used "requests<=2.8.1" then everything would work fine... unless you have some need of 2.8.1 specifically in smart-open?
The text was updated successfully, but these errors were encountered: