RetroSearch Browse

Fri Jul 28 06:49:48 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-July/067766.html

On 7/27/06, Phillip J. Eby <pje at telecommunity.com> wrote:
>
> Personally, I would prefer to see it properly fixed in 2.5 rather than
> having to rip it out.  It's more work for me to create the proper fix than
> it is to just work around it in my code, but it seems a more righteous
> labor, if you know what I mean.  It also means that already-shipped and
> distributed versions of my code would work with the 2.5 release.

Based on this comment, is it really acceptable to just document a
behaviour change?  ISTM there should really only be 2 choices:  fix
2.5 properly or revert the change.  This seemed to be Armin's
position.

n

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-July/067766.html below:

[Python-Dev] Release manager pronouncement needed: PEP 302 Fix