<div class="gmail_quote">On Tue, Jun 9, 2009 at 8:31 AM, Lie Ryan <span dir="ltr"><<a href="mailto:lie.1296@gmail.com">lie.1296@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Maybe python should issue some kind of warning when a module being<br>
imported from a local path has the same name as an installed module? It<br>
is never a good idea to name a module the same as an installed library<br>
unless you're deliberately trying to shadow the library for some reason<br>
(in which case you're a fully consenting adult).<br>
<div><br></div></blockquote></div><br>so I guess it would search the library, then local path, and warn and import if it finds from the local path?<br><br>That's one thing that would be useful to borrow from C(?)/C++ - if you import <somelib> then it only looks in the standard location. If you import "somelib" then it looks in the local path and if it's not found it looks in the standard location. I think there's some other syntax that only looks for the library locally, too.<br>
<br>I wonder what the BDFL would/has said.<br><br>/me wanders off to see what he can find...<br>-Wayne<br clear="all"><br>-- <br>To be considered stupid and to be told so is more painful than being called gluttonous, mendacious, violent, lascivious, lazy, cowardly: every weakness, every vice, has found its defenders, its rhetoric, its ennoblement and exaltation, but stupidity hasn’t. - Primo Levi<br>