Add support for up to Django 3.1 & Python 3.9 #68
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
|
I'll review here after PR #71 is resolved. Thanks for your contribution! |
# Conflicts: # .travis.yml
|
This was also fixed in #72, my apologies that I hadn't seen this PR before. |
|
Now I've released 2.0.0. Thanks for your contribution! |
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.
Add support to Django 2.2 through Django 3.1 as well as Python 3.8 and 3.9 according to the list of supported versions.
Feature or Bugfix
Purpose
The
postgresql_psycopg2module is removed in Django 3.0 which prevents this library to be used with Django > 2.2. This change should fix it.Issues
Might want to drop Python 2.x and Django 1.x as mentioned in #50