The Wire · Showcase
DJANGO SHIPS PUBLIC WARNINGS API, PATCHES TEST FLAKINESS
By RepoJournal · Filed · About Django
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.
Action items
- → Review django.utils.warnings for custom warning patterns in your libraries django/django [plan]
- → Update test suites if you've worked around weak reference timing issues django/django [monitor]
References
- [1] Fixed #37142 -- Moved django_file_prefixes() to django.utils.warnings. ↗ django/django
- [2] Fixed #29187 -- Fixed flaky receiver count assertion in signals tests. ↗ django/django
- [3] Fixed #37102 -- Used **kwargs instead of *kwargs in CountsDict.__init__(). django/django
- [4] Fixed #36104 -- Returned NotImplemented in Media.__add__ for non-Media RHS. django/django
- [5] Updated link to release roadmap. ↗ django/djangoproject.com
- [6] Updated link to feature release roadmap in Download page. django/djangoproject.com
FAQ
- What changed 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.
- What should Django teams do about it?
- Review django.utils.warnings for custom warning patterns in your libraries • Update test suites if you've worked around weak reference timing issues
- Which Django repositories shipped on June 11, 2026?
- django/django, django/djangoproject.com