#32355: Drop support for Python 3.6 & 3.7.
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Core (Other) | Version: 4.0
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
Replying to [comment:2 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/32355#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.31bbbc36a28c4e226e63fb7b2491c151%40djangoproject.com.
