Home Original page

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

Ryan Gonzalez rymg19 at gmail.com
Thu Oct 29 16:50:30 EDT 2015 
Why not just check the path of the imported modules and compare it with the Python library directory?

On October 29, 2015 3:26:08 PM CDT, Mark Roseman <mark at markroseman.com> wrote:
>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
>
>_______________________________________________
>Python-Dev mailing list
>Python-Dev at python.org
>https://mail.python.org/mailman/listinfo/python-dev
>Unsubscribe:
>https://mail.python.org/mailman/options/python-dev/rymg19%40gmail.com

-- 
Sent from my Nexus 5 with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20151029/75458036/attachment.html>
More information about the Python-Dev mailing list