[Python-Dev] time critical: issue 7902 and 2.6.6rc2 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Tue Aug 17 01:45:46 CEST 2010
- Previous message: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
- Next message: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Aug 17, 2010 at 5:15 AM, Barry Warsaw <barry at python.org> 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 clear on that. So I think we should keep the fix. Sounds good to me. Thanks for weighing in.
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.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
- Next message: [Python-Dev] time critical: issue 7902 and 2.6.6rc2
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]