#25881: Mark Python 3.2 in Django 1.8 as unsupported at the end of 2016
------------------------------------------------+------------------------
Reporter: timgraham | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
As discussed on [https://groups.google.com/d/topic/django-
developers/eMu5UQpUdWs/discussion 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.
--
Ticket URL: <https://code.djangoproject.com/ticket/25881>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.20cb74907c7bd61a2fee70f3251b75a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
