Opened 11 minutes ago
#37465 assigned Cleanup/optimization
Drop support for Python 3.12 & 3.13
| Reported by: | Natalia Bidart | Owned by: | Natalia Bidart |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Django 6.2 LTS, supported until April 2030, is the last version to support:
- Python 3.12 (end of life: October 2028)
- Python 3.13 (end of life: October 2029)
Per DEP 20, each feature release supports the two Python versions receiving bug fixes at the start of its pre-release phase, plus the most recent one to have moved to security fixes only. Django 2028 therefore supports Python 3.14, 3.15, and 3.16.
See our policy about Python version support. For Django 2028, the dates work out like this:
- Django 2028 is released in January 2028 and reaches end of life in December 2030.
- Python 3.14, its oldest supported Python, was released in October 2025 and gets five years of upstream support, so it reaches end of life in October 2030.
The same holds every year: Django 2029 supports 3.15 through 3.17, and 3.15 reaches end of life in October 2031, two months before 2029 does in December 2031.
Note:
See TracTickets
for help on using tickets.