After thinking a bit more: Are there any concrete reasons to drop 3.4/3.5 aside from new features? Sure, security is an issue, but looking at the issues with cookie parsing we would have been better off by immediately fixing ourself instead of waiting for python (same goes for XML). So in the end, while I usually advocate for security and up2date systems, I do not think we gain much by dropping python 3.4 and/or 3.5.
I cannot speak for everyone else, but I do have the feeling that Django will get somewhat annoying to deploy for me (Don't get me wrong, I am getting paid to do that, but other people are not in such a lucky situation and I'd still like to see Django grow in enterprise environments). We are on RedHat 7, which I'll certainly stay on for a while. I can probably fetch newer python versions from IUS, but then I'll have to recompile mod_wsgi etc… Given that RedHat does not package Django at all, I am running from the upstream releases, which is perfectly fine for me -- but it would be great if I can use somewhat newer Django versions too. In the end (in my experience), people are using Django everywhere and part of the usage also comes from the fact that it's not that hard to deploy for sysadmins since python is available anywhere; compiling a new Python + infrastructure around it is something else again and requires a lot of change requests in some companies. No matter how we decide, I'd like to see python 3.4 supported on Django 2.0 to ensure that people that wanna upgrade can at least try the first py3-only version without having to upgrade their systems (Ubuntu Trusty is still on 3.4 and still supported). And then maybe try to get some feedback from some companies and the versions of python they are using on Django 2.0. 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/6f7124e6-e00a-4cf6-9fca-91ee1c8dd91c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
