Upgrade to Django 5, Trixie base image, Python3.13, all deps, pylama#1935
Merged
Upgrade to Django 5, Trixie base image, Python3.13, all deps, pylama#1935
Conversation
mxsasha
changed the title
mxsasha
force-pushed
the
ncsc2025upgrade
branch
4 times, most recently
from
937bcea to
fa82d92
Compare
mxsasha
changed the title
mxsasha
changed the title
aequitas
reviewed
Feb 24, 2026
Collaborator
aequitas
left a comment
aequitas
left a comment
There was a problem hiding this comment.
Looks good. We might make the step to a pyproject.toml file and a uv.lock file to fully use uv and drop using the Debian system provided Python. I don't know if that is something you want in this PR already, but then we can drop the UV_SYSTEM_PYTHON and UV_BREAK_SYSTEM_PACKAGES and just manage the python version from pyproject.toml.
Collaborator
Author
Let's include it, we're changing so many packages anyways. |
mxsasha
force-pushed
the
ncsc2025
branch
4 times, most recently
from
dbd8b27 to
fcfd9bf
Compare
aequitas
force-pushed
the
ncsc2025upgrade
branch
from
f9b4fe6 to
fa82d92
Compare
mxsasha
force-pushed
the
ncsc2025
branch
9 times, most recently
from
3301948 to
6249526
Compare
mxsasha
force-pushed
the
ncsc2025upgrade
branch
from
fa82d92 to
dae00c8
Compare
- Django 4 LTS is ending soon, upgrade to 5.2 LTS - Django 5 no longer supports Python 3.9 - Upgrade base image to Debian trixie to get 3.13 - Upgrade all Python dependencies, also for 3.13 support. - Some minor code changes to account for removed Python APIs and other changes. - Change dev version number to meet new requirements This requires the sslyze rewrite, old nassl does has difficulties on trixie.
Pylama has a PR for Python 3.12+ open for 2 years This includes a few code changes due to small style variances.
mxsasha
force-pushed
the
ncsc2025upgrade
branch
from
cbf0ba4 to
e3ea051
Compare
mxsasha
changed the title
mxsasha
force-pushed
the
ncsc2025upgrade
branch
from
e3ea051 to
337bea8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thinking we might not put this in 1.11.0, maybe 1.11.1, just to not make the release too huge. No merge for now. This requires the sslyze rewrite, legacy nassl does has difficulties on trixie. Therefore, this is on top of ncsc2025 branch.
Just wanted to upgrade Django to 5.2, snowballed a bit.
APIs and other changes.
3.13 has support for another 3 years. 3.10 is about to end, 3.9 had already ended. Django 5.2 is supported for 2 years.