On Fri, Jun 4, 2010 at 1:11 AM, Éric Araujo <report@bugs.python.org> wrote:
>
> Sorry for writing when tired. Clearer first sentence: If it does not change the code to match the docs or to fix a regression from an older version, it’s a feature.

This is the biggest problem with rigidness Python process. In this
specific case the patch doesn't make Python any more unstable and
according to policy it won't be integrated into Python 2.7 unless
release manager chooses otherwise. But! release manager is
overwhelmed, so it is VERY unlikely that he will include this patch,
because it is a distraction, and there are always more important stuff
to judge. In addition RM can be incompetent in this particular part of
Python dist and just couldn't take the risk of making random
decisions.

To resolve this bottleneck and help release managers make decisions,
community members should be able to vote on patches. Then release
managers could be able to make releases that satisfy more Python
users. In addition the part of this decision for particular component
of Python dist could be delegated to component maintainers preserving
RM's right to veto any opinion.