#32355 closed Cleanup/optimization (fixed)
Drop support for Python 3.6 & 3.7.
Reported by: | Mariusz Felisiak | Owned by: | Mariusz Felisiak |
---|---|---|---|
Component: | Core (Other) | Version: | 4.0 |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Django 3.2 LTS, supported until April 2024, is the last version to support:
- Python 3.6 (end of life: December 2021)
- Python 3.7 (end of life: June 2023)
See our policy about Python version support and discussions regarding the Python version support policy:
Change History (22)
comment:1 by , 4 years ago
Version: | → 4.0 |
---|
follow-up: 3 comment:2 by , 4 years ago
comment:3 by , 4 years ago
Replying to Claude Paroz:
With my usual conservative hat on, I'd plead to not drop Python 3.7 support too soon. It's still widely used in stable systems (namely Debian) and asking contributors running those systems to install a Python version "by hand" to contribute to Django master branch is not friendly at all.
I understand your concerns, but there's not consensus to change the policy on the mailing list. Also, if not in Django 4.0 then we will need to support Python 3.7 to Django 4.2 LTS (end of life April 2026), so 2 more years, and almost 3 years after the last Python 3.7 release.
comment:4 by , 4 years ago
I know my practice (using latest released Django on as-much-stable-as-possible systems) is not on the majority side, so you'll never find a consensus to change the policy.
comment:7 by , 4 years ago
Triage Stage: | Accepted → Ready for checkin |
---|
With my usual conservative hat on, I'd plead to not drop Python 3.7 support too soon. It's still widely used in stable systems (namely Debian) and asking contributors running those systems to install a Python version "by hand" to contribute to Django master branch is not friendly at all.