The Wire · Showcase
Django fixes release note, clears default ordering confusion
By RepoJournal · Filed · About Django
A single-word fix in a release note clarifies a behavior change that could have tripped up upgrade teams.
Django shipped a one-word correction to a release note [1], fixing the description of a behavior change that clears default ordering after QuerySet combination. The note had said "before" when the change actually happens "after" combination, a distinction that matters for anyone tracking ORM behavior across Django 5.x. The fix, authored by Jacob Walls [2], is tied to tickets #37258 and #36644. It doesn't affect code, but it prevents misreading of the official docs during upgrade planning. Meanwhile, the asv benchmarking repo quietly added ubuntu-latest results [3], a housekeeping commit that keeps performance tracking current for CI. Nothing here is urgent, but the release note correction is worth knowing before you lean on that documented behavior.
One email a day. Unsubscribe in one click.
Keep up with Django in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Review Django 5.x release notes for the corrected default ordering behavior before relying on it django/django [plan]
- → No action needed for django-asv; just note the new ubuntu-latest results in CI django/django-asv [monitor]
References
- [1] Refs #37258, #36644 -- Fixed release note for clearing default ordering after combination. django/django
- [2] Refs #37258, #36644 -- Fixed release note for clearing default ordering after combination. ↗ django/django
- [3] Results for ubuntu-latest added [skip ci] django/django-asv