Django: Versioning Overhaul and Duplicate Fix Cleanup

Django merged foundational support for calendar versioning ahead of the 2028 release scheme change, alongside a cluster of geospatial field fixes and a reminder that duplicate pull requests for the same ticket are landing in the queue.

Duration: PT2M30S

Episode overview

This episode is a short developer briefing from Django.

It explains recent repository work in plain language.

  • Show: Django
  • Published: 2026-09-05T13:04:43Z
  • Audio duration: PT2M30S

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 September 5th, 2026, and this is Django.

The headline today is groundwork for a major release change. Starting in 2028, Django moves to calendar versioning under DEP 20. Nessita's merged pull request, 21886, adds that support now: version tuples gain feature, patch, status, and iteration attributes, and the old five-component comparisons are deprecated. A…

Second theme: geospatial correctness. Three separate pull requests from Saikat and Yassin Bahri touch spatial fields this cycle—preventing expression assignment errors on spatial fields in 21893, blocking undefined SRID transforms from silently writing null values in 21890, and documenting the existing behavior of…

Third, a process note worth flagging: pull requests 21891 and 21892 are duplicate submissions from the same author, Noxtimo, fixing the same generic inline formset issue—tickets 19255 and 18357. Same pattern with 21888 and 21895 from vladimirnani, both addressing gzip compression of bodyless responses under ticket…

Also notable: VimalN2005's new qualname helper in module loading, now reused by migration serializers instead of duplicated path-extraction logic—a small maintainability win. And Huwaiza's…

Wh…

Nearby episodes from Django

  1. Calendar Versioning Lands, Quiet Correctness Fixes Follow
  2. Query Correctness Fixes Land in the Same Window
  3. Equality Checks Get an Overhaul
  4. Correctness Fixes Cluster Around Regressions
  5. Widening the Browser Test Net
  6. Weekly Recap - Data Integrity, Query Correctness, and Duplicate Submissions
  7. Query Correctness Takes Center Stage
  8. Sharper Test Feedback, One Bug at a Time