Home Original page

[Python-Dev] If you shadow a module in the standard library that IDLE depends on, bad things happen

Laura Creighton lac at openend.se
Thu Oct 29 16:35:36 EDT 2015 
In a message of Thu, 29 Oct 2015 13:26:08 -0700, Mark Roseman writes:
>Laura, I think what you want should actually be more-or-less doable in IDLE.
>
>The main routine that starts IDLE should be able to detect if it starts correctly (something unlikely to happen if a significant stdlib module is shadowed), watch for an attribute error of that form and try to determine if shadowing is the cause, and if so, reissue a saner error message.
>
>The subprocess/firewall error is occurring because the ‘string’ problem in your example isn’t being hit right away so a few startup things already are happening. The point where we’re showing that error (as a result of a timeout) should be able to check as per the above that IDLE was able to start alright, and if not, change or ignore the timeout error.
>
>There’ll probably be some cases (depending on exactly what gets shadowed) that may be difficult to get to work, but it should be able to handle most things.
>
>Mark


Mark, how splendid.

Need I submit a bug report/feature request to get this happening?

Very, very pleased to have mentioned it ...

Laura
More information about the Python-Dev mailing list