test against minimum/dev versions of Pallets libraries #4341
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
During the rollout of the 2.0 major version, these were removed because they were always out of sync. Add them back in.
This revealed an incompatibility once Werkzeug 2.1 is released, since it removed
as_tuplebut Flask's test client still passes it. Given that users have already been seeing a deprecation warning from Werkzeug, I'm adding the deprecation here as well, to be removed in Flask 2.1.as_tuplewould return(environ, response), now aTestResponseinstance is always returned.response.request.environhas the same information.