I would like to voice my support for Florian's arguments. It's not only RedHat, Debian is also concerned. The current Jessie stable version which will be supported probably until mid-2018 is Python 3.4, and the upcoming stable version will most probably be Python 3.5. So a strong -1 for dropping 3.5 for Django 2.0. For Python 3.4, we might bring the issue to the technical board. Dropping Python 2 will already be a strong progress and might allow nice improvements for Django.
Claude Le mardi 27 décembre 2016 21:25:39 UTC+1, Florian Apolloner a écrit : > > 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 > -- 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/fb8c83ee-c050-4d48-8db5-a8244c9cb489%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
