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.

Author larry
Recipients BreamoreBoy, benjamin.peterson, brett.cannon, eli.bendersky, eric.snow, larry, ncoghlan, serhiy.storchaka, skrah, techtonik
Date 2013-11-24.22:58:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385333930.59.0.566763532841.issue19655@psf.upfronthosting.co.za>
In-reply-to
Content
The rule is, no new features.  Bug and security fixes from now on.

It isn't always clear whether or not something is a new "feature".  In the case of such ambiguity, the decision is up to the sole discretion of the release manager.

If you seriously want to check in this thing (*sigh*), I'll take a look at it.  But you'll have to point me at either a patch that applies cleanly to trunk, or a repository somewhere online with the patch already applied to trunk.

Something like a code refactor is probably okay during betas, but during RCs I would really prefer we keep checkins strictly to a minimum.
History
Date User Action Args
2013-11-24 22:58:50larrysetrecipients: + larry, brett.cannon, ncoghlan, techtonik, benjamin.peterson, eli.bendersky, skrah, BreamoreBoy, eric.snow, serhiy.storchaka
2013-11-24 22:58:50larrysetmessageid: <1385333930.59.0.566763532841.issue19655@psf.upfronthosting.co.za>
2013-11-24 22:58:50larrylinkissue19655 messages
2013-11-24 22:58:50larrycreate