Django 1.8 is the last version to support Python 3.2. Python 3.2 is 
scheduled to be end of life at February 2016 [1] while Django 1.8 is 
scheduled to be supported until April 2018. The latest security release for 
the 3.2 series, Python 3.2.6 contained a regression that causes 30 admin 
test failures in the Django test suite related to parsing of httponly 
cookies. I'm not sure if this problem is limited to the test client or if 
it has the potential to cause problems in a web server context (if anyone 
is using Python 3.2.6, I'd be interested to know). I submitted a patch to 
Python to correct the issue [2], but it appears unlikely that the patch 
will be applied along with a new release (no response from Python 3.2 
release manager in 1 year).

Due to the test failures, we cannot run the Django test suite with Python 
3.2 on the Ubuntu 14.04 CI machines which use the deadsnakes PPA [3] to 
install the latest version of Python (3.2.6). Therefore the tests are 
limited to running on our one remaining Ubuntu 12.04 CI machine which 
includes Python 3.2.3 (deadsnakes doesn't bundle versions of Python that 
would override the one included by the distribution). Support for Ubuntu 
12.04 ends April 2017, so we shouldn't keep that machine longer than that.

Options:
1. Drop Python 3.2 support for Django 1.8 sometime before Django 1.8 EOL
2. Keep Python 3.2 support until Django 1.8 EOL:
  a. Don't worry about CI support and rely on local testing of security 
fixes (we had the same situation with Django 1.4 and Python 2.5)
  b. Install the latest non-broken Python 3.2 release (3.2.5) "manually" 
(without using deadsnakes) on the newer CI servers
3. Your idea

Thanks for your feedback!

[1] https://www.python.org/dev/peps/pep-0392/
[2] https://bugs.python.org/issue22758
[3] https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes

-- 
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/34dd15c4-dba5-46fe-9ac0-6d5a426db2df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to