Django: GIS Cleanup and Stricter Model Checks
Django activity centered on geographic stack maintenance for the 6.2 release and tighter model validation, with early proposals for reporting queries and session expiry. Two documentation fixes were merged, while the G-DAL drop, PostGIS revert, and model checks remain under review.
Duration: PT2M26S
Episode overview
This episode is a short developer briefing from Django.
It explains recent repository work in plain language.
- Show: Django
- Published: 2026-09-21T13:05:30Z
- Audio duration: PT2M26S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's Monday, September 21st, 2026, and this is your Django briefing.
The signal today is steady hardening before Django 6.2, with cleanup in the geographic stack and stricter checks in the model system.
First, geographic libraries. Pull request 22005 proposes dropping support for G-DAL versions 3.3 and 3.4, which would be more than five years old when 6.2 ships next April. Alongside that, pull request 22003 reverts a workaround for a PostGIS bug, noting that PostGIS 3.5.4 fixed the issue last October. And merged…
Second, model validation. Pull request 22007 extends system check E-zero-25 to flag when a property is overridden by a related-field accessor, including properties on abstract parents, while keeping the allowed inherited case. Relatedly, pull request 22008 adds protection against a clash where an auto-generated…
Finally, query and request handling. Pull request 22006 is draft-only documentation for proposed grouping sets, roll-up, cube and grouping support for reporting queries that need detail rows, subtotals and grand totals. Pull request 22010 would bring custom expiry to signed-cookie sessions, supporting browser-close,…
What's next: expect discussion on…
Nearby episodes from Django
- Weekly Recap - Schema Fixes, ORM Edge Cases, and Platform Cleanup
- Composite Key Compiler Fixes and Input Hardening
- Closing the Gaps in Query and Field Behavior
- Generated Field Fix Gets Walked Back and Rebuilt
- Walking Back a Risky Field Check
- Schema Migrations Get More Careful
- Better Error Messages, Clearer Exceptions
- Admin Search Fix for Inherited Models