On Aug 17, 2010, at 09:45 AM, Nick Coghlan wrote:
>A bit late (since you already cut rc2), but the key point for me is
>that code that is fixed to work correctly on 2.6.6 (where this bug has
>been fixed) will still work on any 2.6.x release.
Yep, thanks.
-Barry
signature.asc
Description: PGP si
On Tue, Aug 17, 2010 at 5:15 AM, Barry Warsaw wrote:
> On Aug 16, 2010, at 09:56 AM, Guido van Rossum wrote:
>
>>Sounds to me like the fix is legit, and the bug it uncovered was a
>>real bug and should have been caught. There really is no justification
>>to consider it a feature -- the PEP is clea
On Aug 16, 2010, at 11:54 AM, Barry Warsaw wrote:
>Either way, I think we need a 2.6.6rc2 (a thought that's been invading
>my dreams all weekend :). This would push back 2.6.6 final to
>September 12 or 13.
Make that 2.6.6 final on August 24.
-Barry
signature.asc
Description: PGP signature
___
On Aug 16, 2010, at 09:56 AM, Guido van Rossum wrote:
>Sounds to me like the fix is legit, and the bug it uncovered was a
>real bug and should have been caught. There really is no justification
>to consider it a feature -- the PEP is clear on that. So I think we
>should keep the fix.
Sounds good
Sounds to me like the fix is legit, and the bug it uncovered was a
real bug and should have been caught. There really is no justification
to consider it a feature -- the PEP is clear on that. So I think we
should keep the fix.
If it is a gray area, it is only gray because the implementation was
im
For 2.6.6rc1 a patch was committed that addressed bug 7902:
http://bugs.python.org/issue7902
http://svn.python.org/view?rev=81381&view=rev
While this fixes a legitimate bug in Python 2.6, it also changes existing
behavior in the 2.6 series. As 2.6.6 is the last planned maintenance release,
I do
