Who contributed to Django on August 1, 2026?

5 developers shipped this update, including ahmed5145, Jacob Walls, brunifrancesco, mbaragiola, and claudep.

What were the notable Django updates?

Fixed #27734 -- Made parallel test workers reuse database clones of exited workers, Removed advice to include ticket numbers in tests, and Fixed #36626 -- geodjango -- Preserved milliseconds when parsing GPX ….

@django

Python's batteries-included web framework

github ↗

Pick a date

Topics: Python Full archive →

The Wire · Showcase

PARALLEL TEST WORKERS NOW REUSE DATABASE CLONES, KILLING FLAKY TEST RUNS

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

5 people shipped this

Jacob Walls @jacobtylerwalls 2 cited

ahmed5145 @ahmed5145 1 cited

brunifrancesco @brunifrancesco 1 cited

mbaragiola @mbaragiola 1 cited

claudep @claudep 1 cited

Django fixed a critical race condition where respawned test workers would crash trying to connect to non-existent database clones, causing entire parallel test suites to abort.

ParallelTestSuite assigned worker IDs from a monotonically increasing counter, so when multiprocessing.Pool respawned a crashed worker, the replacement incremented past N and tried to connect to a database clone that never existed, fataling the entire run [1]. The fix reuses the database clones from exited workers instead of creating new ones, a pattern developers using parallel testing have been fighting since issue #27734 was opened. This lands alongside cleanup work removing outdated advice to include ticket numbers directly in test code [2]. GeoDjango also landed millisecond precision for GPX timestamp parsing [3] and fixed spatial index alteration on RasterField [4], while core fixes a subtle bug where DatabaseDefault was unexpectedly falling back to Python defaults on multi-table inheritance primary keys [5]. Translation updates rolled across django-localflavor [6].

Action items

→ Upgrade to latest Django if you run parallel tests - this eliminates worker respawn crashes django/django [immediate]
→ Review your test suite comments for removed ticket number guidance django/django [plan]
→ If using GeoDjango with GPX imports or RasterField spatial indexes, test after upgrading django/django [plan]

References

[1] Fixed #27734 -- Made parallel test workers reuse database clones of exited workers. ↗ django/django
[2] Removed advice to include ticket numbers in tests. django/django
[3] Fixed #36626 -- geodjango -- Preserved milliseconds when parsing GPX … ↗ django/django
[4] Fixed #37236 -- Allowed altering spatial indexes on RasterField. ↗ django/django
[5] Fixed #37238 -- Fixed unintentional fallback to python default for a db_default. ↗ django/django
[6] Updated translations from Transifex ↗ django/django-localflavor

Quick answers

What shipped in Django on August 1, 2026?: Django fixed a critical race condition where respawned test workers would crash trying to connect to non-existent database clones, causing entire parallel test suites to abort. In total, 9 commits and 8 pull requests landed.
Who contributed to Django on August 1, 2026?: 5 developers shipped this update, including ahmed5145, Jacob Walls, brunifrancesco, mbaragiola, and claudep.
What were the notable Django updates?: Fixed #27734 -- Made parallel test workers reuse database clones of exited workers, Removed advice to include ticket numbers in tests, and Fixed #36626 -- geodjango -- Preserved milliseconds when parsing GPX ….

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 3

DJANGO FIXES NULL TIME FIELD HANDLING IN GEOSPATIAL MAPPING

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

python 3 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.