Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#25881 closed Cleanup/optimization (fixed)

Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016

Reported by: Tim Graham Owned by: nobody
Component: Documentation Version: 1.8
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

As discussed on django-developers, there doesn't seem to be much value in supporting Python 3.2 well after it's end of life in February 2016.

Change History (4)

comment:1 Changed 4 years ago by Tim Graham

Has patch: set

comment:2 Changed 4 years ago by Tim Graham <timograham@…>

Resolution: fixed
Status: newclosed

In e6bd688e:

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

comment:3 Changed 4 years ago by Tim Graham <timograham@…>

In 14e1e53a:

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

Backport of e6bd688ef3b58ee522794dce77f64a81b53b3b9e from master

comment:4 Changed 4 years ago by Tim Graham <timograham@…>

In 5eeb8edf:

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

Backport of e6bd688ef3b58ee522794dce77f64a81b53b3b9e from master

Note: See TracTickets for help on using tickets.
Back to Top