[Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013 (original) (raw)
Benjamin Peterson benjamin at python.org
Mon Mar 25 21:40:33 CET 2013
- Previous message: [Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013
- Next message: [Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2013/3/25 Todd Rovito <rovitotv at gmail.com>:
Python 2.7.4 release candidate was just announced and is ready for testing here: http://python.org/download/releases/2.7.4/
Now the clock is ticking and we have two weeks to get IDLE issues pushed into CPython before the final release of 2.7.4.
I'm afraid the ship has sailed on that. After a bugfix release candidate, I only take patches that fix regressions from earlier releases of the same series. (The goal is to not make any changes between the release candidate and final release.) Assuming PEP 343 becomes policy, IDLE changes can land for 2.7.5, which will be in approximately 6 months.
-- Regards, Benjamin
- Previous message: [Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013
- Next message: [Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]