Re: Python 3.5 Support in Django 1.8.x?

Never mind, just saw that 3.5 is listed in the 1.8 release notes and answered my own question. -- 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

Re: Python 3.5 Support in Django 1.8.x?

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? On Tue, Oct 27, 2015 at 5:19 PM, Ned Batchelder

Re: Python 3.5 Support in Django 1.8.x?

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

Re: Python 3.5 Support in Django 1.8.x?

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

Re: Python 3.5 Support in Django 1.8.x?

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

Re: Python 3.5 Support in Django 1.8.x?

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

Re: Python 3.5 Support in Django 1.8.x?

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 On Sat, 24 Oct 2015 at 03:28 Marc Tamlyn wrote: > FWIW, I think we should add 3.5 support to 1.8. > > On 23 October 2015 at 17:08, Tim Graham

Re: Python 3.5 Support in Django 1.8.x?

FWIW, I think we should add 3.5 support to 1.8. On 23 October 2015 at 17:08, Tim Graham 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

Re: Python 3.5 Support in Django 1.8.x?

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

Python 3.5 Support in Django 1.8.x?

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