Update codebase for Django 3 and Python 3.8 #62
Merged
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
moh-moola
approved these changes
Mar 2, 2020
|
4.4.1 should be released shortly. We've been using this in production for a while and happy with it, so I'll move development status to Production/Stable |
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.
Added configurations to
travis.yml,setup.pyandtox.inito account for the various compatibility versions between Django and Python (as listed here on the Django website)setup.pyto aid discoverabilityCHANGELOG.rstto add compatibility for Django 3 and Python 3.8. Also corrected a couple of typos4 - Betainsetup.py. Is there any reason why this is still in Beta? I'll let you change it if you think it is ready to be changed to5 - Production/StableSince the default branch is
develop, I have made the PR against it.Please feel free to make any changes as you see fit and squash the commits if you think is neater.
Once all of the tests have passed, will you be updating
masterand releasing a new version to PyPI to account for the changes?