Django 1.8 was the last version to support Python 3.2, which has its 
security updates end February 2016. That means Python 3.2 users can 
continue getting Django security updates for about 2 years after Python 
security updates end. I am wondering if we should instead try to better 
align the end of Python support with the end of Django support? (By the 
way, Django 1.4 supports Python 2.5 which had its security updates end Oct 
2011 and since we had trouble configuring Jenkins with Python 2.5, we broke 
compatibility a couple times in recent security releases -- now I run the 
tests locally as needed).

Let's take Python 3.3 as an example. Security updates for Python 3.3 are 
scheduled to end in September 2017. Django 1.8 supports 3.3 and will 
receive updates until April 2018. Given anyone using 3.3 is covered by the 
LTS, I'm inclined to drop 3.3 support now (in Django 1.9). Alternatively, 
the next two major releases of Django will be supported until April 2017 
and December 2017. 

I don't find Django support for 3.3 to be a big burden, but there are 
occasional issues such as new features in 3.4 that are missing and need to 
be backported for 3.3 (today I ran into a pull request with a need for 
glob.escape(), so we needed a backport that works on Python 2 and Python 
3.3). The other consideration is that Python 3.5 will be released in 
September, so we'd be back to 3 versions of Python 3 for Jenkins to test 
against.

Are there any users of Python 3.3 out there who find that there are big 
obstacles to upgrading to 3.4?

I think it's useful to plan ahead a bit to try to avoid cases such as the 
enterprise users who are now stuck on Python 2.6 and Django 1.6.

-- 
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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/5494ca68-c62b-4205-98e1-144471de9d97%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to