[Python-Dev] [python-committers] Python 3.3.7 release schedule and end-of-life (original) (raw)
Victor Stinner victor.stinner at gmail.com
Thu Aug 31 04:22:37 EDT 2017
- Previous message (by thread): [Python-Dev] PEP 539 (second round): A new C API for Thread-Local Storage in CPython
- Next message (by thread): [Python-Dev] Inplace operations for PyLong objects
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hello,
2017-07-15 23:51 GMT+02:00 Ned Deily <nad at python.org>:
To that end, I would like to schedule its next, and hopefully final, security-fix release to coincide with the already announced 3.4.7 security-fix release. In particular, we'll plan to tag and release 3.3.7rc1 on Monday 2017-07-24 (UTC) and tag and release 3.3.7 final on Monday 2017-08-07. In the coming days, I'll be reviewing the outstanding 3.3 security issues and merging appropriate 3.3 PRs. Some of them have been sitting as patches for a long time so, if you have any such security issues that you think belong in 3.3, it would be very helpful if you would review such patches and turn them into 3.3 PRs.
Any update on the 3.3.7 release? 3.3.7rc1 wasn't released yet, no?
By the way, it seems like a recent update of libexpat caused a regression :-( https://bugs.python.org/issue31170 I didn't have time to look on that issue yet.
Victor
- Previous message (by thread): [Python-Dev] PEP 539 (second round): A new C API for Thread-Local Storage in CPython
- Next message (by thread): [Python-Dev] Inplace operations for PyLong objects
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]