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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. 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/1ed824c7-4775-4951-a00c-5223ac431cf5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
