Ok, I created a ticket to track cleanups and new Python features we can use when Python 3.4 support is removed: https://code.djangoproject.com/ticket/27857
We can evaluate that a bit later in the Django 2.0 release cycle and decide whether or not to keep Python 3.4 support for 1.11. On Wednesday, January 18, 2017 at 12:20:13 PM UTC-5, Rotund wrote: > > I agree that allowing more people to be able to do development against > Django 2.0 is important. That stated, please be very explicit in the > release notes and documentation that "Versions below Python 3.6 are > expected to be dropped before the next Django LTS will be released, so > please keep that in your project planning." (Language too informal, but I > think the idea is correct.) > > > > On Wed, Jan 18, 2017 at 2:28 AM, Claude Paroz <[email protected] > <javascript:>> wrote: > >> Le mardi 17 janvier 2017 15:48:46 UTC+1, Tim Graham a écrit : >>> >>> I propose to tentatively target Python 3.5+ for Django 2.0 but not to >>> remove the current workarounds for Python 3.4 at this time. Shortly before >>> the alpha for Django 2.0, an interested person can look into how much work >>> is required to fix any test failures on Python 3.4 and we'll make a >>> decision then. >>> >> >> I'm strongly advocating for keeping 3.4 support for now, as I would have >> difficulty to continue contributing to Django. >> My main system is still using 3.4 and will be for some months. Even if I >> could rather easily installing manually a more recent Python, I very much >> like relying on my stable distro packages. Sorry for my dumbness! >> >> Claude >> >> -- >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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/09570028-4eea-41ac-b364-93ae2c946b21%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/09570028-4eea-41ac-b364-93ae2c946b21%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Joe Tennies > [email protected] <javascript:> > -- 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/fb3704d2-c069-41d2-beb0-445524c6f0aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
