-
-
Notifications
You must be signed in to change notification settings - Fork 354
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
responses==0.23.2 breaks pip resolution with popular packages #654
Comments
@jmsanders responses pins requests >= 2.30, for the reason of compatibility between 2.29 and urllib 2.x however, I think it is user issue if some lower boundaries are not pinned. In this case boto should be pinned to >=x |
Not sure if have to pin Note 2.30.0 is the requests version that added support for urllib 2.0. https://github.com/psf/requests/releases/tag/v2.30.0 From release notes: Users who wish to stay on urllib3 1.x can pin to urllib3<2. |
responses==0.23.2 forces us onto urllib>=2.0.0 which causes a whole new pip resolution chain. getsentry/responses#654 Pinning until all of these packages support urllib3>=2.0.0
responses==0.23.2 forces us onto urllib>=2.0.0 which causes a whole new pip resolution chain. getsentry/responses#654 Pinning until all of these packages support urllib3>=2.0.0
Describe the bug
This may ultimately end not being a
responses
issue (or a "just pin to the old version" answer), but I wanted to call to your attention thatresponses==0.23.2
substantially changes pip resolution results when installed alongside other popular packages.Given:
psf/requests#6432
and boto/botocore#2926
Perhaps #652 is premature?
Additional context
No response
Version of
responses
0.23.2
Steps to Reproduce
Results in:
Whereas:
Will backtrack through many, many versions of boto3 and eventually land on:
Expected Result
Pip resolution succeeds with recent versions of other packages.
Actual Result
Pip resolution takes a long time and installs very old versions of other packages.
The text was updated successfully, but these errors were encountered: