build: Added minimal versions of Django/Flask for unit tests. #837
Conversation
This file contains 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
daniel-sanche
approved these changes
Jan 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Using the constraints file of each individual Python version to provide for minimum versions of Django and Flask that work for the integrations we provide with both libraries (lots of
DeprecationWarningswere raised)The minimum version of Django that is officially supported for each version of Python is documented here: (https://docs.djangoproject.com/en/5.0/faq/install/#what-python-version-can-i-use-with-django), while Flask took a lot more tuning to get to as close to 1.0.0 as possible (the main challenge is figuring out appropriate versions of its sister dependencies
werkzeug,jinja2,markupsafe, anditsdangerous.Documentation updates will happen in a future PR.