Support Flask 2.3 #189
Merged
Support Flask 2.3 #189
+9
−7
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
temp workaround to prevent the error after downgrading Flask as in replit#188 (better would be to support Flask 2.3 and not use deprecated features)
noneofyourbusiness1415252
requested review from
cdmistman
and removed request for
a team
blast-hardcheese
approved these changes
Dec 8, 2023
|
Thank you! |
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.
To support Flask 3.0 would require us to change the version constraint for
Werkzeugaccordingly, so that would be a breaking change.Why
prevent errors due to deprecated features (as seen in #188 in the part after Flask was downgraded as
poetrywanted)What changed
Support 2.3 by accounting for the deprecation of
json_encoderTest plan
Rollout