Fix DEFAULT_FILE_STORAGE/STATICFILES_STORAGE in django 4.2 #256
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.
Description
Describe:
DEFAULT_FILE_STORAGE / STATICFILES_STORAGE are deprecated on django 4.2+
When using pytest-django (and in other circumstances) django settings are basically evaluated twice: one when triggering
app_helper.utils._make_settings
and one by pytest-django.Adding legacy and new settings in the exclusion list in pytest compatibility function, we ensure only one setting is evaluated
References
Fix #255
Checklist
inv lint
changes
file included (see docs)