Enable middleware decorator to work in newer versions of Django#16
Merged
Conversation
Member
Author
|
@philgyford have a look! Turned out to be similar to what we discussed. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Resolves #6
django-webmentionprovides both an old-style and a new-style middleware, but the provided decorator wrapped only the old-style middleware. By inheriting fromdjango.utils.deprecation.MiddlewareMixin, the middleware and the decorator become compatible with both styles.Leaving the standalone new-style middleware in for backward compatibility as well. Dropping support for Python 3.5 because Django 3.0+ no longer supports it.
Adding automation for releasing to GitHub releases and PyPI as I hadn't done that prior.