Django: Walking Back a Risky Field Check

The team reversed a system check on generated fields after discovering it encouraged a behavior-breaking change, while also landing a long-awaited template syntax improvement and two documentation clarifications.

Duration: PT2M21S

Episode overview

This episode is a short developer briefing from Django.

It explains recent repository work in plain language.

  • Show: Django
  • Published: 2026-09-17T13:06:14Z
  • Audio duration: PT2M21S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good day, and welcome to Django, your developer briefing for September 17th, 2026.

Today's biggest story is a course correction. Back when Django added a system check warning that "null" has no effect on generated fields, the advice seemed harmless. It wasn't. Nessita's PR 21983 reverts that check entirely, because acting on the warning changed real behavior: negated lookups would stop matching…

Second theme: long-standing template limitations are finally getting addressed. Sarah Boyce's PR 21982 allows multiline template tags, continuing work that stalled on a previous pull request. Two old tickets, one from years back, get closed out here. If you write custom templates or maintain large template files,…

Rounding out the day, two documentation fixes worth knowing about even though they're small. PR 21981 adds a note to the JSON field docs warning that PostgreSQL's native jsonb type does not preserve object key order — worth remembering if your code depends on key ordering in stored JSON. And PR 21980 corrects the…

What's next: watch for the generated field check to potentially return in a safer form, and expect follow-up cleanup now that multiline template tags are in. Both areas…

Tha…

Nearby episodes from Django

  1. Schema Migrations Get More Careful
  2. Better Error Messages, Clearer Exceptions
  3. Admin Search Fix for Inherited Models
  4. Weekly Recap - Security Hardening & Platform Cleanup
  5. Trimming the Edges — Old Databases and Old Queries
  6. Cookie Security Fix and a Flood of Duplicate PRs
  7. Cookie Prefix Safety Check
  8. When Duplicate Fixes Flood the Queue