This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
Upgrade to Django 3.1 #80
Comments
dirn
added a commit
that referenced
this issue
Oct 17, 2020
The only dependency not being updated here, at least not fully, is Django. That's going to be done separately as part of #80. For now the version is being fixed to the latest version of 3.0.
dirn
added a commit
that referenced
this issue
Oct 17, 2020
The only dependency not being updated here, at least not fully, is [Django]. That's going to be done separately as part of #80. For now the version is being fixed to the latest version of 3.0. The Django version also has to be set for the development requirements. Without doing so, the latest version would be pulled in by [django-debug-toolbar]. This would lead to conflicting versions in CI as some of the [tox] environments install both the development and regular dependencies. [django]: https://www.djangoproject.com [django-debug-toolbar]: https://pypi.org/p/django-debug-toolbar [tox]: https://tox.readthedocs.io
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Django 3.1 is now available.
Should we take advantage of async views? This change should be done independently of the upgrade itself.
When doing the upgrade, we can potentially remove the dependency specifier from
dev-requirements.in. Alternatively, we may want to keep it around and just change it to>=3.1,<3.2in both places.The text was updated successfully, but these errors were encountered: