Merged
Conversation
'shooting in the dark' edition, i.e. just upgrading the version number without RTFM and seeing if the CI still runs
This probably means we'll move to Django 5.2 no sooner than October 2025. See https://docs.djangoproject.com/en/5.2/faq/install/
… the 'auto imported' warning 30 objects imported automatically (use -v 2 for details).
reverts (the meat of) c51051d
vanschelven
force-pushed
the
main
branch
6 times, most recently
from
3a14c5e to
6266f15
Compare
as per the comment: possible from Django 5.0 up
vanschelven
force-pushed
the
django-5-2
branch
from
97e97c7 to
d155fa2
Compare
made possible by Django 5.2
(analogous to the parent commit) made possible by Django 5.2
it doesn't support the relevant machinery
Contributor
Author
|
Database version requirement notes (to be included on our own release notes): Minimums (per Django 5.2)
What distros actually ship (sqlite)
|
vanschelven
added a commit
that referenced
this pull request
Nov 11, 2025
….2 upgrade this method wasn't changed upstream. See #89
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
1 participant
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.
With Bugsink dropping Python 3.9 support we can move forward on this.
[x] Check the release-notes for all versions up to 5.2 (breaking changes, features removed) -- no action required.
[x] Tests still run
[x] Use new features where applicable (as previously pointed out in comments)
[ ] Actually test this in live settings, i.e. not just running the automated tests
(I will merge-into-main before seriously doing that last point, and then will use
mainin serious environments for a while before making a release)