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-06-11
stories 13

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

DJANGO SHIPS PUBLIC WARNINGS API, PATCHES TEST FLAKINESS

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

Django moved its internal warning utility into a public API, letting developers emit custom warnings while cleanly skipping Django's stack frames.

The framework extracted django_file_prefixes() from django.utils.deprecation into a new django.utils.warnings module [1], making it officially available for third-party code that needs to emit RuntimeWarning or UserWarning without cluttering Django's internals. This is a meaningful quality-of-life improvement for library authors who've been reaching into private APIs to do exactly this. In parallel, Django fixed a long-standing flaky test in its signals suite [2] where weak reference cleanup timing caused intermittent receiver count assertion failures, making the test suite more reliable going forward. The core library also corrected two smaller issues: CountsDict now properly accepts keyword arguments [3], and Media.__add__ now returns NotImplemented for non-Media operands [4], improving operator behavior consistency. Documentation updates to djangoproject.com point users directly to the feature release roadmap [5] [6] instead of routing through deprecated wiki links.

Quick answers

What shipped in Django on June 11, 2026?
Django moved its internal warning utility into a public API, letting developers emit custom warnings while cleanly skipping Django's stack frames. In total, 7 commits and 6 pull requests landed.
Who contributed to Django on June 11, 2026?
2 developers shipped this update, including ZhengKangYang and jacobtylerwalls.
What were the notable Django updates?
Fixed #37142 -- Moved django_file_prefixes() to django.utils.warnings, Fixed #29187 -- Fixed flaky receiver count assertion in signals tests, and Fixed #37102 -- Used **kwargs instead of *kwargs in CountsDict.__init__().