On 04/02/2013 12:57 AM, Ned Deily wrote:
> 2. Roger, is this issue new to 2.7.4, 3.2.4, or 3.3.1?
No, this bug has been baked into IDLE since the beginning. See line 215 
http://hg.python.org/cpython/file/30713d5288df/Lib/idlelib/ColorDelegator.py
>   How likely do you think it will be seen by users?
For Windows users using pythonw.exe, it would cause IDLE to immediately 
terminate due to issue13582. On Linux and Mac, the errors would write to 
stderr, though not likely be visible to the end user. On Linux and Mac 
the error is not "harmful" since IDLE still remains perfectly usable. 
The error does not leave IDLE in an inconsistent state.
>   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?
I'm ok with cherry-picking it into the final, but in the interest of 
simplicity, I'd recommend deferring it to the next maintenance release. 
There are other bugs, like #8900 that are easier to trigger than this one.