Imo we should not drop Python versions overeagerly. After all I do not wanna compile our own python for djangoproject.com :D Given that Redhat is on Python 3.4 for the foreseeable future, I'd actually even like to see 3.4 still supported in Django 2.0 unless there is a good reason to drop it. Fwiw, Ubuntu Trusty which is LTS and still supported also is on Python 3.4. So unless there are compelling arguments to drop 3.4, lets keep it as long as it is not too much work.
Either way, I am completely against dropping Python 3.5 now -- lets make the Django 2.0 migration not more painful than it has to be (ie I do not want to force people to upgrade existing supported systems just to get the latest python and therefor Django). Cheers, Florian On Tuesday, December 27, 2016 at 4:12:57 PM UTC+1, Tim Graham wrote: > > When I drafted the 1.11 release notes in May, I wrote, "The next major > release, Django 2.0, will only support Python 3.5+." > > Our Python version support policy is "Typically, we will support a Python > version up to and including the first Django LTS release whose security > support ends after security support for that version of Python ends." > > Python 3.5's EOL is September 2020 which I think is sufficiently close to > Django 1.11's EOL of April 2020 that we could say Django 2.0 is Python > 3.6+. The alternative is not to drop Python 3.5 compatibility until Django > 2.2 LTS which is supported until April 2022. I don't see much advantage to > that. Any objections? > > p.s. There is already a ticket suggesting to take advantage of a Python > 3.6 feature: > https://code.djangoproject.com/ticket/27635* - *django.utils.crypto > should use secrets on Python 3.6+ > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f1da2b09-0309-46e6-9a7c-75ea9cd6f91b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
