Larry Hastings added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19655> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
