$ the-wire · showcase
UnorderedObjectListWarning points at user code again
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
Django's three-item day is a small correctness fix worth knowing about: the unordered-queryset warning now blames your code instead of Django's, plus documentation and CI follow-ups.
Fixed #28219 -- Made UnorderedObjectListWarning skip Django frames. django/django
UnorderedObjectListWarning used a fixed stacklevel=3, which only landed on user code when Paginator was instantiated directly; pagination through ListView, the admin, or AsyncPaginator produced a traceback pointing inside Django. The warning now uses skip_file_prefixes=django_file_prefixes(), the pattern Django already applies to other warnings, so the traceback resolves to the queryset you lef...
Fixed #28219 -- Made UnorderedObjectListWarning skip Django frames. django/django
The same fix landed on main as Fixed #28219, making it available in the next release rather than only as a proposal.
Fixed #37397 -- Clarified DATA_UPLOAD_MAX_MEMORY_SIZE behavior on request.body vs request.POST. django/django
The docs for DATA_UPLOAD_MAX_MEMORY_SIZE now spell out how the limit applies to request.body versus request.POST, the ambiguity that has bitten people reading large raw bodies.
Skipped 1-element geometry collection tests on all Oracle versions. django/django
One-element geometry collection tests are skipped on all Oracle versions, after later Oracle 19c builds reproduced the same failures noted in an earlier commit; Oracle users lose nothing, since the tests, not the feature, were the problem.
Fixed #37294 -- Added Firefox and WebKit to daily SQLite Playwright CI. django/django
Daily SQLite Playwright CI now runs Firefox and WebKit alongside Chromium, and the rest of the day was housekeeping: a Djangonaut Space issue template on djangoproject.com, ubuntu-latest benchmark results in django-asv, and a working-group meeting note.
