December 4, 2025
Batteries included, takes reloaded
Django 6 Released
Fans cheer, skeptics squint, and the framework wars reignite
TLDR: Django 6 lands with built-in security tools and support for the newest Python, while nudging developers off older setups. Fans praise its all-in-one simplicity, skeptics question the jump to big version numbers, and the comments devolve into a lively framework roll call—Django vs everything else.
Django 6 just dropped and the comments section immediately turned into a roll call of web dev tribes. One poster kicked off a “show of hands” for who’s on big frameworks like Django/Rails, who’s in the micro-camp (Flask), who’s enterprise (Java/.NET), who’s all-JavaScript, and who’s off-road with Go or Rust. Translation: the framework wars are back, baby.
Meanwhile, the love letters poured in. Fans called Django’s batteries-included approach a no-brainer for projects big and small, with one user simply declaring they enjoy using it, full stop. On the facts: Django 6 supports the latest Python versions (3.12–3.14), nudges the ecosystem to drop older setups, and adds built-in Content Security Policy (CSP)—a security feature that tells browsers what’s safe to load to block sneaky scripts. That last part got nods for making security less scary out of the box.
But there’s drama: one commenter wondered why the shift to big “6.0” versions and even asked if it’s a response to declining popularity. Spicy! Others just posted the official blog link and moved on, like: here’s the news, keep calm and ship. Read the release notes and the blog while the thread argues over who chose the “right” framework.
Key Points
- •Django 6.0 was released on December 3, 2025, with official release notes.
- •Django 6.0 supports Python 3.12, 3.13, and 3.14; Django 5.2.x is the last to support Python 3.10 and 3.11.
- •Built-in Content Security Policy (CSP) support is introduced, including middleware, a context processor for nonces, and configuration settings.
- •CSP policies are configured via SECURE_CSP and SECURE_CSP_REPORT_ONLY using Python dictionaries and Django-provided constants.
- •Third-party authors are advised to drop support for Django versions prior to 5.2 and run tests with python -Wd to resolve deprecations for 6.0 compatibility.