➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mark.dickinson
Recipients csernazs, eric.smith, mark.dickinson
Date 2010-02-11.18:48:52
SpamBayes Score 1.701707e-05
Marked as misclassified No
Message-id <1265914135.15.0.754309801865.issue7906@psf.upfronthosting.co.za>
In-reply-to
Content 
> Is there any chance to get those changes you mentioned backported to 2.6?

Actually, to be honest, I'm not sure that backporting these changes to the release branch is a good idea.  Is this bug causing problems in real code (besides the test suite)?

It seems to me that this bug is fairly harmless, and the backport of the 2.7 behaviour could have unintended consequences (seems unlikely, but it's always difficult to be sure :);  I'm tempted suggest closing it as a 'won't fix', especially given that it's already fixed in 2.7.
History
Date User Action Args
2010-02-11 18:48:55mark.dickinsonsetrecipients: + mark.dickinson, csernazs, eric.smith
2010-02-11 18:48:55mark.dickinsonsetmessageid: <1265914135.15.0.754309801865.issue7906@psf.upfronthosting.co.za>
2010-02-11 18:48:53mark.dickinsonlinkissue7906 messages
2010-02-11 18:48:52mark.dickinsoncreate