Uh oh!
There was an error while loading. Please reload this page.
Escalate the distinction between data=... and content=... to be stricter. - #1573
Merged
Conversation
florimondmanca
approved these changes
Apr 14, 2021
Merged
8 tasks
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 freeto 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.
Currently we're supporting
data=<bytes|text|bytes-iter|async-byte-iter>for requests compatibility,although we're recommending against it.
I think we ought to escalate this into a more formal deprecation warning, and then remove it entirely.
Having a stricter, more consistent API here feels like a clear improvement to me vs
requests.