[django] Remove MIDDLEWARE_CLASSES deprecation warning from tests #444
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
… just had our test/sample project set up incorrectly to have both a MIDDLEWARE and a MIDDLEWARE CLASSES when django >= (1,10). The warning wasn't present in 2.0 but was shown for earlier new-middlware versions.
palazzem
approved these changes
Mar 28, 2018
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.
We just had our test/sample project set up incorrectly to have both a redundant MIDDLEWARE_CLASSES as well as a MIDDLEWARE when django >= (1,10). The warning wasn't present in 2.0 but was shown for earlier new-middlware versions.
I just made it only use MIDDLEWARE_CLASSES for supported versions.