Fixed #25881 -- Marked Python 3.2 in Django 1.8 as unsupported at the end of 2016.
This commit is contained in:
parent
a8614fb438
commit
e6bd688ef3
|
@ -45,7 +45,7 @@ What Python version can I use with Django?
|
||||||
============== ===============
|
============== ===============
|
||||||
Django version Python versions
|
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**
|
**1.9, 1.10** **2.7, 3.4, 3.5**
|
||||||
============== ===============
|
============== ===============
|
||||||
|
|
||||||
|
|
|
@ -6,6 +6,15 @@ Django 1.8.8 release notes
|
||||||
|
|
||||||
Django 1.8.8 fixes several bugs in 1.8.7.
|
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
|
Bugfixes
|
||||||
========
|
========
|
||||||
|
|
||||||
|
|
|
@ -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**
|
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.
|
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
|
What's new in Django 1.8
|
||||||
========================
|
========================
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue