test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

[1.9.x] Fixed #25881 -- Marked Python 3.2 in Django 1.8 as unsupported at the end of 2016. 

Backport of e6bd688ef3 from master
This commit is contained in:
Tim Graham 2015-12-07 14:27:16 -05:00
parent c341db1d83
commit 5eeb8edfbb
3 changed files with 13 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faq/install.txt
View File

@ -45,7 +45,7 @@ What Python version can I use with Django?
============== ===============
Django version Python versions
============== ===============
1.8 2.7, 3.2, 3.3, 3.4, 3.5
1.8 2.7, 3.2 (until the end of 2016), 3.3, 3.4, 3.5
**1.9, 1.10** **2.7, 3.4, 3.5**
============== ===============

9
docs/releases/1.8.8.txt
View File

@ -6,6 +6,15 @@ Django 1.8.8 release notes
Django 1.8.8 fixes several bugs in 1.8.7.
Python 3.2 users, please be advised that we've decided to drop support for
Python 3.2 in Django 1.8.x at the end of 2016. We won't break things
intentionally after that, but we won't test subsequent releases against Python
3.2 either. Upstream support for Python 3.2 ends February 2016 so we don't find
much value in providing security updates for a version of Python that could be
insecure. To read more about the decision and to let us know if this will be
problematic for you, please read the `django-developers thread
<https://groups.google.com/d/topic/django-developers/eMu5UQpUdWs/discussion>`_.
Bugfixes
========

3
docs/releases/1.8.txt
View File

@ -28,6 +28,9 @@ Python compatibility
Django 1.8 requires Python 2.7, 3.2, 3.3, 3.4, or 3.5. We **highly recommend**
and only officially support the latest release of each series.
Due to the end of upstream support for Python 3.2 in February 2016, we won't
test Django 1.8.x on Python 3.2 after the end of 2016.
What's new in Django 1.8
========================