Open browniebroke opened 3 years ago
I'd recommend either updating deprecated and new Python / Django versions or strictly replicating what the package currently supports.
I've aimed at adding all versions supported by the package currently:
Django 3.2 doesn't pass the build at the moment, seems to require a bit more work, so I left it out of this change.
I've aimed at adding all versions supported by the package currently:
3.7 is not in the current list of supported Python versions.
Updated
@farhan0581 what do you think? Since I opened this, Python 3.6 has reached EOL, so we might want to drop it as well. However, before doing further work I'd like to see if you agree with the approach first (I'd rather drop versions in a separate pull request, if you don't mind).
Setup CI with GitHub actions. Since it's a new workflow added from a fork, it doesn't run on this pull request but you can see the build result in the actions tab of my fork.