Closed huydbui closed 3 years ago
I did some research. The very first one was djangorestframework only supports upto django 3.0. Case closed. Sorry about this.
https://www.django-rest-framework.org Seems latest DRF support Django 3.1. Any plan for go with Django 3.1?
It's not only about DRF, but all our django libraries. I'm going to start a table that I'll keep up to date to gather where are our dependencies, taken from @emilepetrone idea in #2352:
Base.txt
Name | Version in Master | 3.1 Compatible Version | OK |
---|---|---|---|
pytz | 2020.4 | n/a | ✅ |
python-slugify | 4.0.1 | n/a | ✅ |
Pillow | 8.0.1 | n/a | ✅ |
rcssmin | 1.0.6 | n/a | ✅ |
argon2-cffi | 20.1.0 | n/a | ✅ |
whitenoise | 5.2.0 | 5.2.0 | ✅ |
redis | 3.5.3 | n/a | ✅ |
celery | 4.4.6 | n/a | ✅ |
django-celery-beat | 2.1.0 | 2.1.0 | ✅ |
flower | 0.9.5 | n/a | ✅ |
uvcorn | 0.12.2 | n/a | ✅ |
django-environ | 0.4.5 | ❓ | |
django-model-utils | 4.1.1 | 4.1.0 | ✅ |
django-allauth | 0.44.0 | ❓ | |
django-crispy-forms | 1.10.0 | 1.10.0 | ✅ |
django-compressor | 2.4 | ❓ | |
django-redis | 4.12.1 | unreleased | ⏱ |
djangorestframework | 3.12.2 | 3.11.1 | ✅ |
django-cors-headers | 3.6.0 | 3.4.5 | ✅ |
local.txt
Name | Version in Master | 3.0 Compatible Version | OK |
---|---|---|---|
Werkzeug | 1.0.1 | n/a | ✅ |
ipdb | 0.13.4 | n/a | ✅ |
psycopg2 | 2.8.6 | n/a | ✅ |
watchgod | 0.6 | n/a | ✅ |
mypy | 0.790 | n/a | ✅ |
django-stubs | 1.7.0 | unreleased | 🕒 |
pytest | 6.1.2 | n/a | ✅ |
pytest-sugar | 0.9.4 | n/a | ✅ |
sphinx | 3.3.1 | n/a | ✅ |
flake8 | 3.8.4 | n/a | ✅ |
coverage | 5.3 | n/a | ✅ |
black | 20.8b1 | n/a | ✅ |
pylint-django | 2.4.0 | 2.3.0 | ✅ |
pylint-celery | 0.3 | n/a | ✅ |
pre-commit | 2.8.2 | n/a | ✅ |
factory-boy | 3.2.0 | 3.2.0 | ✅ |
django-debug-toolbar | 3.2.0 | 3.0 | ✅ |
django-extensions | 3.1.0 | 3.0.4 | ✅ |
django-coverage-plugin | 1.8.0 | ❓ | |
pytest-django | 4.1.0 | 3.10.0 | ✅ |
production.txt
Name | Version in Master | 3.0 Compatible Version | OK |
---|---|---|---|
gunicorn | 20.0.4 | n/a | ✅ |
Collectfast | 2.2.0 | ❓ | |
sentry-sdk | 0.19.3 | n/a | ✅ |
hiredis | 1.1.0 | n/a | ✅ |
django-storages | 1.10.1 | 1.10 | ✅ |
django-anymail | 8.1 | 7.2 | ✅ |
@browniebroke
many packages already update to Django 3.1 support, can regenerate test matrix please p.s. how you do this matrix ?)
can regenerate test matrix please
I'm not generating it, I took the table from the Django 3.0 issue and updated versions manually. It's quite tedious but we don't need to do this too often. If someone has a script, it would be helpful...
many packages already update to Django 3.1 support
Which ones are missing? I'm updating the message as I merge updates, but it's possible that I missed one.
django-environ looks like we don't even need to wait https://github.com/joke2k/django-environ/issues/239#issuecomment-718918143
django-allauth they added Django 3.1 to Travis/tox which I don't know what this means (testing?)
django-compressor I don't see an issue reported regarding Django 3.1 Django Compressor is compatible with Django 1.11 and newer.
django-stubs looks like this one is still a no no
django_coverage_plugin I don't see an issue reported regarding Django 3.1
Collectfast I don't see an issue reported regarding Django 3.1
Feel free to send a pull request 👍
Just found out that django-stubs
was missing https://github.com/typeddjango/django-stubs/pull/558 and it's now merged. Next release should be good to go.
Feel free to send a pull request 👍
I'm not that advance of a github user just yet. I'll be there.
PR opened here https://github.com/pydanny/cookiecutter-django/pull/3043
I haven't seen anyone asked this question yet. So I'll go first. Is it ok now to upgrade to django 3.1.x?
Another newbie question: beside the tests that I wrote, is there any other test that I could run to make sure the django-cookiecutter on my computer works with django 3.1.1?
Thank you.