mir-backend-python-djangolisted
Install: claude install-skill anantbhandarkar/make-it-right
# /mir-backend-python-django · Make It Right (Django)
Bottom tier of the chain: `mir-backend` (generic gates) → `mir-backend-python` (CPython runtime model) → **this** (Django/DRF library mechanics). Run the gates first; load the Python runtime tier for the concurrency/process model; reach for *this* at Gate 5 (design mechanics), Gate 6 (implementation), and Gate 7 review. **Runtime-level concerns (GIL, async-vs-sync, blocking the event loop, fork-safe pools, cold start) live in `mir-backend-python` — not here.**
**Stack assumed**, versions verified 13 Aug 2026:
| | Version | Notes |
|---|---|---|
| Current release | **Django 6.1**, released 5 Aug 2026 | Mainstream support to Apr 2027, extended to Dec 2027. Requires **Python 3.12–3.14**. |
| Current LTS | **Django 5.2 LTS** | Extended support to **Apr 2028**. Last line to support Python 3.10/3.11. |
| Previous | Django 6.0 | Mainstream support ended 4 Aug 2026 — security-only now. |
| Next LTS | Django 6.2 LTS, due Apr 2027 | |
Django 6.1 also dropped PostgreSQL < 15, MySQL < 8.4, MariaDB < 10.11, and SQLite < 3.37. Rest of the stack: DRF · PostgreSQL (psycopg 3) · Celery, or the built-in `django.tasks` framework added in 6.0. **Say which Django version the project is on before applying any of this** — 5.2 and 6.1 differ materially in the ORM and in the background-task story.
## The Django footguns AI walks into most
These are the stack-specific cousins of the failure-mode catalog. Each is something Django/DRF code gets