Relax requirements to allow requests >=2.11 and <3.0 - #178
Merged
Conversation
Contributor
Author
|
@stephenmcd please reconsider your former choices to nuke pull requests of this ilk. I have done exactly as you requested and pinned it to less than 3. Your choice of "only allow versions of requests that I have personally tested" causes far more problems than it solves. If there's a version of requests that breaks your module, in the future, we can always blacklist that version then. |
Contributor
|
Thank you! |
1 similar comment
Contributor
Author
|
Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requests 2.x will remain API compliant, while still allowing for fixes in versions of
requests that are newer than 2.11.1. Tested with 2.13 and 2.14, works fine.