On 7/27/06, Phillip J. Eby <[EMAIL PROTECTED]> 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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
