-
-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[deps] Add support for django 3.2 #280
Comments
I would like to work on this. |
Go for it! Look at here to get an idea of what needs to be done: |
@yashikajotwani12 I thought about this and I think @pandafy was working on this, please coordinate with him to avoid you two working on the same thing at the same time. However, I think you could start with upgrading django-x509 to the latest versions of DJango: openwisp/django-x509#122 (we'll need to upgrade django-x509 and openwisp-users before we can upgrade openwisp-controller). |
Okay!! I would start working on upgrading django-x509, and would also ask @pandafy to avoid working on the same thing. Thank you! |
Thank you so much. |
No worries he'll be doing only openwisp-users for now. |
- Bumped django-allauth to 0.45.0 - Bumped django-reversion to use latest master branch Closes #280
- Bumped django-allauth to 0.45.0 - Bumped django-reversion to use latest master branch Closes #280
- Bumped django-allauth to 0.45.0 - Bumped django-reversion to use latest master branch Closes #280
- Bumped django-allauth to 0.45.0 - Bumped django-reversion to use latest master branch Closes #280
Created follow up issue for django 4.0 support: #292. |
Let's make sure this module can run with Django 3.2 and Django 4.0 alpha.
The text was updated successfully, but these errors were encountered: