Django: ASGI Middleware Fix and Async Cleanup
Django merged a fix to reduce per-middleware context switching under ASGI, with related async resource cleanup in progress. The day also brought modernization moves, database reliability fixes, and a docs reorganization.
Duration: PT2M39S
Episode overview
This episode is a short developer briefing from Django.
It explains recent repository work in plain language.
- Show: Django
- Published: 2026-09-24T13:05:06Z
- Audio duration: PT2M39S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning, it's September 24th, 2026, and this is your Django briefing.
The headline is async performance and correctness, with a merged fix to cut unnecessary context switching for middleware under A S G I.
That change, in pull request 21523, stops relying on the generic middleware mix-in async path for each middleware, which had defeated the base handler's goal of transitioning only once per chain.
For developers running async, that means less overhead per request and more predictable threading behavior, while Django's own middleware now opts into the leaner path by default to limit breakage.
Related work continues in pull request 22025, which wraps async iteration sites in async closing helpers to ensure generators and streams are cleaned up properly.
A second theme is modernization and cleanup.
Nearby episodes from Django
- Model Edge Cases and Driver Docs
- File Move Race Fix and Sitemap Docs
- GIS Cleanup and Stricter Model Checks
- Weekly Recap - Schema Fixes, ORM Edge Cases, and Platform Cleanup
- Composite Key Compiler Fixes and Input Hardening
- Closing the Gaps in Query and Field Behavior
- Generated Field Fix Gets Walked Back and Rebuilt
- Walking Back a Risky Field Check