$ the-wire · showcase
DJANGO CLEARS JSONRESPONSE DOCS, DEP 20 MOVES TO ACCEPTED
By RepoJournal · Filed · About Django · Composed from the cited sources · methodology
Django's documentation team fixed outdated guidance on JSONResponse's deprecated safe parameter, while the core team formally accepted DEP 20 for standardizing how the framework handles async patterns.
Two commits landed to correct stale JSONResponse documentation [1][2] that still described the safe parameter as defaulting to True, contradicting the deprecation that shipped in 6.2. The docstring and reference docs have now been updated to match current behavior, closing out ticket #36905 cleanly. In parallel, DEP 20 [3][4] moved from Draft to Accepted status, a signal that Django's async story is settling into its final form. The community working group also captured June and July meeting minutes [5], documenting the governance discussions that drive these decisions. Light day across the stack: 4 commits and 2 PRs. Nothing breaking, nothing urgent, just cleanups and process grinding forward.
Action items
- → Review DEP 20 accepted changes if you maintain async middleware or database adapters django/deps [plan]
- → Update any internal docs that reference JSONResponse safe parameter behavior django/django [monitor]
References
- [1] Refs #36905 -- Fixed outdated docs for JSONResponse safe parameter. ↗ django/django
- [2] Refs #36905 -- Corrected safe param in JSONResponse signature in docs. ↗ django/django
- [3] Marked DEP 20's status as Accepted. ↗ django/deps
- [4] Marked DEP 20's status as Accepted. (#116) ↗ django/deps
- [5] Add June & July meeting minutes ↗ django/online-community-working-group
