➜

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 ned.deily
Recipients Todd.Rovito, benjamin.peterson, ezio.melotti, georg.brandl, larry, ned.deily, orsenthil, rhettinger, roger.serwy, terry.reedy
Date 2013-04-02.05:57:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1364882255.43.0.190353426481.issue17613@psf.upfronthosting.co.za>
In-reply-to
Content 
I'm able to reliably reproduce the exception using your test procedure, Roger, using either current head of 3.3 or 2.7, and am not able to reproduce it with stop_colorizer.patch applied.  LGTM.  So it seems to me the next questions are:

1. Raymond, does this seem like a plausible scenario for the failures you've seen?  And if you apply the patch, do you see any further failures?

2. Roger, is this issue new to 2.7.4, 3.2.4, or 3.3.1?  How likely do you think it will be seen by users?  And what is your recommendation to the release managers about including the patch in any or all of the pending maintenance releases, understanding that the options are to cherry-pick into the final and hope for the best, cherry-pick it and do an RC2, or defer the fix to the next maintenance releases?
History
Date User Action Args
2013-04-02 05:57:35ned.deilysetrecipients: + ned.deily, georg.brandl, rhettinger, terry.reedy, orsenthil, larry, benjamin.peterson, ezio.melotti, roger.serwy, Todd.Rovito
2013-04-02 05:57:35ned.deilysetmessageid: <1364882255.43.0.190353426481.issue17613@psf.upfronthosting.co.za>
2013-04-02 05:57:35ned.deilylinkissue17613 messages
2013-04-02 05:57:34ned.deilycreate