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.

@django

Python's batteries-included web framework

github ↗

Pick a date

Topics: Python Full archive →

The Wire · Showcase

DJANGO FIXES NULL TIME FIELD HANDLING IN GEOSPATIAL MAPPING

By RepoJournal · Filed 06:55 UTC on August 3, 2026 · About Django

1 person shipped this

Jacob Walls @jacobtylerwalls 2 cited

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.

Action items

→ Verify LayerMapping usage with null time fields in your geospatial models django/django [plan]
→ Monitor main branch for the next Django release containing this fix django/django [monitor]

References

[1] Fixed #37242 -- Fixed reading null time fields in LayerMapping. django/django
[2] Fixed #37242 -- Fixed reading null time fields in LayerMapping. ↗ django/django

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.

DJANGO 6.1 LANDS. CHANNELS AND DOCS READY.

Django 6.1 is officially released, and the entire ecosystem has already cut over: Channels pinned the stable dependency, the ticket tracker flipped to 6.1 as default, and the download page went live.

python 19 shipped

@django Aug 5

DJANGO PATCHES FOUR CRITICAL VULNERABILITIES IN ADMIN AND SPATIAL QUERIES

Django shipped fixes for four CVEs overnight, including a stored XSS in admin URL rendering that could compromise staff accounts and three denial-of-service vectors in geolocation and language handling.

python 10 shipped

@django Aug 4

DJANGO ADDS FREE-THREADED PYTHON 3.14T TO POSTGIS CI

Django is validating free-threaded Python 3.14t against GIS tests, signaling serious commitment to the no-GIL future.

python 14 shipped

@django Aug 2

DJANGO-LOCALFLAVOR 5.1 SHIPS WITH VATIN VALIDATOR FIX

Django-localflavor bumped to 5.1 [ref:4], capping a release cycle that fixed a typo in the VATINValidator that could have caused validation edge cases.

python 4 shipped

Elsewhere on the wire

AI Agents Aug 6

LANGCHAIN HARDENS ANTHROPIC TOOL CALLING AND GIT CREDENTIALS AS OPENHANDS SHIPS 1.10.0

LangChain fixed a critical credential leak in evaluation runs while Anthropic tool schemas get proper fallback handling, as three major agent frameworks push releases across the ecosystem.

ai-agents 54 shipped

Local LLMs Aug 6

OLLAMA FIXES KV CACHE CORRUPTION, LLAMA.CPP HARDENS FILE SEARCH, VLLM KILLS MOE LEGACY CODE

Ollama patched a critical cache corruption bug that corrupts lazy snapshots during multi-request prefills, while llama.cpp hardened Windows junction traversal and vLLM removed 14 hardcoded MoE shards across quantization methods.