-
Notifications
You must be signed in to change notification settings - Fork 138
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
Update Django to next LTS #2734
Comments
Initial pyproject.toml change against current testing branch poetry.lock (after
And given:
We have two additional, incidental, updates along the way. WraptChangelog: https://wrapt.readthedocs.io/en/latest/changes.html
Charset-normalizerChangelog: https://github.com/Ousret/charset_normalizer/blob/master/CHANGELOG.md
|
Post Django update we have 78 new WARNINGS:
And 5 new test failures: With the following repeated many times:
...Ran 278 tests in 29.091s FAILED (errors=5)
|
https://docs.djangoproject.com/en/dev/releases/3.0/#features-removed-in-3-0 Looks to be our culprit, with the above suggested new format:
The 'RemovedInDjango40Warning' warnings are extremely numerous as they pertain to our entire url definitions, attempting to address here to avoid a large amount of warning logging spam. |
We may also be subject to: https://docs.djangoproject.com/en/dev/releases/3.0/#features-removed-in-3-0
Working on removing the forest of warnings and staticfiles messages first. |
See: https://docs.djangoproject.com/en/3.2/releases/3.2/#customizing-type-of-auto-created-primary-keys All warnings etc can be view via:
for our:
|
Thus far we now have, from django-admin test:
And we have a full test suite pass:
|
Update to Django 3.2.23, with incidental minor update to latest wrapt & charset-normalizer. # Includes - Required move to "load static" from "load staticfiles" in base/setup.html. - Settings option for DEFAULT_AUTO_FIELD: models.W042 - Project wide move from url to re_path: RemovedInDjango40Warning.
Closing as: |
This represents a blocker for our Py3.10 Milestone (https://github.com/rockstor/rockstor-core/milestone/25) and we have issue (#2696) which may limit us to Py3.10 for now. Plus our current Py3.9 is itself a blocker for our Tumbleweed-aarch64 target (see: #2693) preventing our next Stable release.
Canonical issue for Milestone: https://github.com/rockstor/rockstor-core/milestone/24
From: https://docs.djangoproject.com/en/4.2/faq/install/#what-python-version-can-i-use-with-django
we have:
Where-as our current Django is at its end re Python compatibility, representing a Python update blocker as-is:
From: https://docs.djangoproject.com/en/3.2/faq/install/#what-python-version-can-i-use-with-django
The text was updated successfully, but these errors were encountered: