This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: state of the 3.3 branch unclear
Type: security Stage:
Components: Interpreter Core Versions: Python 3.3
process
Status: closed Resolution: out of date
Dependencies: Superseder:
Assigned To: Nosy List: brett.cannon, georg.brandl, wiz
Priority: normal Keywords:

Created on 2016-06-26 12:47 by wiz, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg269282 - (view) Author: Thomas Klausner (wiz) * Date: 2016-06-26 12:47
https://www.python.org/dev/peps/pep-0398/ mentions that a 3.3.7 release was planned for February 27, 2016. It appears this never happened.

It also mentions that there will be source-only security updates for 3.3.x until September 2017. However, it appears that for example https://bugs.python.org/issue22417 from 2014 was never fixed for 3.3.x.
(perhaps it did not affect 3.3.x, but it affected 2.7 and 3.4, so the chances are high it did)

I'm not particularly interested in a release -- I'm fine with declaring 3.3.x end-of-life, but the documentation should match the reality.
Thanks.
msg269295 - (view) Author: Brett Cannon (brett.cannon) * (Python committer) Date: 2016-06-26 16:17
New releases of Python 3.3 are on hold pending a security fix: https://mail.python.org/pipermail/python-dev/2016-February/143400.html
History
Date User Action Args
2022-04-11 14:58:33adminsetgithub: 71577
2016-06-26 16:17:15brett.cannonsetstatus: open -> closed

nosy: + georg.brandl, brett.cannon
messages: + msg269295

resolution: out of date
2016-06-26 12:47:32wizcreate