[Python-Dev] Simple IDLE issues to commit before Python 2.7.4 release in two weeks on 4/6/2013
Todd Rovito
rovitotv at gmail.com
Tue Mar 26 01:54:41 CET 2013
More information about the Python-Dev mailing list
Tue Mar 26 01:54:41 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 ]
On Mon, Mar 25, 2013 at 4:40 PM, Benjamin Peterson <benjamin at python.org> wrote: > 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. Benjamin, No problem we can wait 6 months. I should of read the dev guide section about Python releases before I sent the email.
- 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 ]
More information about the Python-Dev mailing list