126 wires and counting

$ follow Django

Keep up with Django in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-03
stories 3

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

DJANGO FIXES NULL TIME FIELD HANDLING IN GEOSPATIAL MAPPING

By RepoJournal · Filed · About Django · Composed from the cited sources · methodology

LayerMapping now correctly reads null time fields after a follow-up alignment with OFTDate and OFTDateTime value properties.

Jacob Walls landed a fix for issue #37242 that resolves incorrect handling of null time fields in Django's LayerMapping geospatial utility [1]. The patch brings the `OFTTime` implementation into alignment with existing `value` properties on `OFTDate` and `OFTDateTime` [2], ensuring consistent null handling across temporal field types. This follow-up to an earlier commit addresses a gap that could cause silent data corruption or unexpected behavior when processing geospatial datasets with missing time values. The fix is targeted but important for anyone using GeoDjango's OGR layer mapping functionality with nullable time columns.

Quick answers

What shipped in Django on August 3, 2026?
LayerMapping now correctly reads null time fields after a follow-up alignment with OFTDate and OFTDateTime value properties. In total, 2 commits and 1 pull requests landed.
Who contributed to Django on August 3, 2026?
1 developer shipped this update, including Jacob Walls.
What were the notable Django updates?
Fixed #37242 -- Fixed reading null time fields in LayerMapping and Fixed #37242 -- Fixed reading null time fields in LayerMapping.