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.
"Adding support" may be a very generous term here, I didn't need to make any changes to the codebase, it was already compatible and all of the tests are passing :)
Description
README
andsetup.py
Related Issue
Not sure this warrants discussing in an issue - if this is the case, I don't mind opening one up, just tell me.
Motivation and Context
It allows all users of
django-simple-history
that want to upgrade to Django 3.1 to upgrade with the confidence that it's supported and helps prevent regression bugs that may be introduced in the future that only affect Django 3.1How Has This Been Tested?
I ran the tests locally and on Travis CI.
Screenshots (if appropriate):
Types of changes
Checklist:
make format
command to format my codeAUTHORS.rst
CHANGES.rst