➜

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 lukasz.langa
Recipients grahamd, lukasz.langa
Date 2012-04-18.12:49:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334753392.84.0.563241010339.issue14590@psf.upfronthosting.co.za>
In-reply-to
Content 
While this bug is real, I'm hesitant to fix it for 2.7 and 3.2. I can imagine someone using the current behaviour unintentionally, and getting burned by the fix. This would be a real PITA to debug.

Is it fine by you if I just fix it for 3.3 and update the backport?
History
Date User Action Args
2012-04-18 12:49:52lukasz.langasetrecipients: + lukasz.langa, grahamd
2012-04-18 12:49:52lukasz.langasetmessageid: <1334753392.84.0.563241010339.issue14590@psf.upfronthosting.co.za>
2012-04-18 12:49:52lukasz.langalinkissue14590 messages
2012-04-18 12:49:52lukasz.langacreate