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-01
stories 17

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

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

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

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

References

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