Remove the dependency on django-secure #2912
Merged
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.
django-secure was merged into Django 1.8, and since rtd.org uses Django 1.9, migrating to using the built-in checks reduces the dependency list and avoids any problems between newer versions of Django and django-secure.
I was looking at the list of dependencies in #2819, noticed that django-secure was a package listed as "not compatible", then went digging in its repo and discovered it was deprecated.