With a little more than a month to go until the Django 2.0 alpha (targeted for September 18), I'd like to make a final decision about whether or not to keep Python 3.4 support for Django 2.0. Jenkins is currently running the tests on pull requests with Python 3.4 and 3.6. I've seen a few times where contributors first used Python 3.5+ syntax and then had to make adjustments for 3.4 compatibility so while it's not a large burden, it's not a non-trivial one.
Has anyone changed their thinking in the last few months? If not, I guess we'll keep Python 3.4 support for Django 2.0 and drop it for 2.1. On Friday, February 17, 2017 at 9:32:20 PM UTC-5, Tim Graham wrote: > > 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 <cla...@2xlibre.net> 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 django-develop...@googlegroups.com. >>> To post to this group, send email to django-d...@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/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 >> ten...@gmail.com >> > -- 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/356d7e07-0be0-4200-a5da-0d092dd2e761%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
