Python 3.5 Support in Django 1.8.x?

[Tim Allen]

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

[Tim Graham]

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.

[Marc Tamlyn]

FWIW, I think we should add 3.5 support to 1.8.

--
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 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.

For more options, visit https://groups.google.com/d/optout.

[Dheerendra Rathor]

In my opinion adding 3.5 support to 1.8 makes sense since 1.8 is LTS and by the end of 2018 we'll have python 3.6 and 3.7 as well 

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1GkMrKnJn9J0HHTqcauMF4gSMH-Bwd-n2beSrCCr9rixg%40mail.gmail.com.

[Russell Keith-Magee]

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 %-)

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAMwjO1GkMrKnJn9J0HHTqcauMF4gSMH-Bwd-n2beSrCCr9rixg%40mail.gmail.com.

[Tim Graham]

You might be surprised at the number of fixes needed for Python 3.5 support (and to silence all deprecation warnings). They're tracked at https://code.djangoproject.com/ticket/23763.

I backported most of them to 1.8 during the 1.8 release cycle, but stopped doing so once 1.8 went final. I don't mind putting together a branch with the rest of the changes to get the build passing on Django 1.8/Python 3.5, but I'm not so sure we'll want to continue this with Python 3.6 and beyond.

[Tim Graham]

Here's the PR to remove 50K lines of deprecation warnings when running the Django 1.8 tests on Python 3.5 as well as to fix the two test failures caused by those warnings: https://github.com/django/django/pull/5472

In case you look and wonder about the build failures, Jenkins broke today after a new release of sqlparse. I submitted a fix: https://github.com/andialbrecht/sqlparse/pull/203

[Ned Batchelder]

BTW, there's a move afoot to reconsider removing inspect.getargspec: http://bugs.python.org/issue20438 and http://bugs.python.org/issue25486

--Ned.

On 10/24/15 10:30 AM, Tim Graham wrote:

Here's the PR to remove 50K lines of deprecation warnings when running the Django 1.8 tests on Python 3.5 as well as to fix the two test failures caused by those warnings: https://github.com/django/django/pull/5472

In case you look and wonder about the build failures, Jenkins broke today after a new release of sqlparse. I submitted a fix: https://github.com/andialbrecht/sqlparse/pull/203

--
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 http://groups.google.com/group/django-developers.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/f13c34f1-d059-4017-8626-41d6d5c3a760%40googlegroups.com.

[James Bennett]

Bumping this thread a bit because I subscribe to Debian's tracker for their Django package, and there's some question of whether we do or do not officially support Python 3.5 on Django 1.8. Was there ever a final decision?

To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/563014A1.7000309%40nedbatchelder.com.

[James Bennett]

Never mind, just saw that 3.5 is listed in the 1.8 release notes and answered my own question.