Closed jmsanders closed 1 year ago
@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 then pip resolver will either fail or install the right revision of responses for you.
Not sure if have to pin urllib3>=2
though. As it is allowed to use requests>=2.30
with urllib3<2
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.
As a note there is issue #657 and PR #659 which are both related to this.
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:
https://github.com/psf/requests/issues/6432 and https://github.com/boto/botocore/issues/2926
Perhaps https://github.com/getsentry/responses/issues/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.