Requests is pinned at 2.12.3, allow it to use a later version
See original GitHub issueI am currently unable to build with pact-python
as I have another library using the latest requests
version 2.12.4
and currently pact-python
has it pinned to 2.12.3
Can the requirement for requests
be changed to requests>=2.12.3
?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Community Updates — Requests 2.28.1 documentation
Running $ python -m requests.help now includes the installed version of idna. Bugfixes. Fixed issue where Requests would raise ConnectionError instead of ...
Read more >New resolver downloads hundreds of different package ...
We do currently pin our pip version, and we've pinned for now at 20.2.4, but not having the option to get any new...
Read more >Requests Documentation - Read the Docs
This wrapper exception provides interoperability for multiple exceptions that may be thrown by different python versions and json serialization ...
Read more >python-requests-2.21.0-3.el7 | Build Info
Information for build python-requests-2.21.0-3.el7. ID, 26193. Package Name, python-requests. Version, 2.21.0. Release, 3.el7. Epoch.
Read more >Tree - rpms/python-requests - Fedora Package Sources
Source0: https://github.com/requests/requests/archive/v%{version}/requests-v ... Allow charset_normalizer 2.1.0 and newer up to 3.0.0 ... Update to 2.12.3.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yep, I think that’s a good next step, we can move things back if we find some time to investigate further.
Would it be acceptable to mark the current pinned versions as minimums and then add upper limits as they arise, rather than try to predict them (unless a specific limit is known about right now, of course)? The reason I say this is that a user of pact-python can always add a requirement to enforce their own upper limit to work around an issue, but they can’t undo a limit that you’ve imposed.