Agreed. This didn’t really affect 1.4 because 2.7 was in a very stable place, and we didn’t support Python 3. Now that we’re Py3 focussed, and Python has a similar backwards compatibility policy to Django (i.e., Python 3.7 isn’t going to break all Python 3.6 code in subtle ways), it makes sense that our LTS will be officially supported.
Russ %-) On Sat, Oct 24, 2015 at 5:57 AM, Marc Tamlyn <marc.tam...@gmail.com> wrote: > FWIW, I think we should add 3.5 support to 1.8. > > On 23 October 2015 at 17:08, Tim Graham <timogra...@gmail.com> wrote: > >> Officially Django 1.8 doesn't support Python 3.5. In practice, I think it >> probably works. See details in >> https://code.djangoproject.com/ticket/25502 about why the 1.8 test suite >> doesn't pass with Python 3.5. We could probably change that if there is >> sufficient interest, however, I'm not aware of a precedent of adding Python >> version support in a major release retroactively. >> >> On Friday, October 23, 2015 at 10:48:54 AM UTC-4, Tim Allen wrote: >>> >>> Since Django 1.9 will support Python 3.5, I was wondering if there are >>> any plans to support Python 3.5 in Django 1.8, since it is an LTR. >>> >>> I did a cursory search and didn't find anything stating yay or nay. I'm >>> going to assume 1.8 only support 3.4 for now, as I've had issues with >>> Python 3.5 (if, on the other hand, there will be support, I'll report this >>> bugs in detail). >>> >>> Can someone give me an answer or point me to a relevant discussion I may >>> have missed? Thank you. >>> >>> Regards, >>> >>> Tim >>> >> -- >> 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 http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/eb6e94aa-eedf-4fff-9d3b-f7ba424c0a71%40googlegroups.com >> <https://groups.google.com/d/msgid/django-developers/eb6e94aa-eedf-4fff-9d3b-f7ba424c0a71%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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 http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAMwjO1GkMrKnJn9J0HHTqcauMF4gSMH-Bwd-n2beSrCCr9rixg%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAMwjO1GkMrKnJn9J0HHTqcauMF4gSMH-Bwd-n2beSrCCr9rixg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJxq84_bc%3DUD0w8zwoF6%3D5R4dc3%3DKOODG2DWDaZv3YusYSY5ag%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
