how to prevent python import from looking into the current directory

[TP]

Hi everybody,

I would like to prevent the loading of modules in the current directory.
For example, if I have a personal module in the current directory
named "os", when I do "import os", I would like Python to import os
standard module, not my personal module of the current directory.
Is this possible?

Thanks
--
python -c "print ''.join([chr(154 - ord(c)) for c in '*9(9&(18%.\
9&1+,\'Z4(55l4('])"

"When a distinguished but elderly scientist states that something is
possible, he is almost certainly right. When he states that something is
impossible, he is very probably wrong." (first law of AC Clarke)

 

[Chris Rebert]

Hi everybody,

I would like to prevent the loading of modules in the current directory.
For example, if I have a personal module in the current directory
named "os", when I do "import os", I would like Python to import os
standard module, not my personal module of the current directory.
Is this possible?

This should do the trick:

import sys
sys.path.remove('')

Cheers,
Chris

 

[TP]

(Could you please set a valid email address for people to contact you
if necessary?)

Thanks a lot for your help.
My email address is in my signature:

--
python -c "print ''.join([chr(154 - ord(c)) for c in '*9(9&(18%.\
9&1+,\'Z4(55l4('])"

"When a distinguished but elderly scientist states that something is
possible, he is almost certainly right. When he states that something is
impossible, he is very probably wrong." (first law of AC Clarke)

 

[Benjamin Peterson]

Hi everybody,

I would like to prevent the loading of modules in the current directory.
For example, if I have a personal module in the current directory
named "os", when I do "import os", I would like Python to import os
standard module, not my personal module of the current directory.
Is this possible?

While the solutions given by others in this thread will work, I think it is best
policy to not name your own modules after stdlib ones. When I see "os"
referenced in code, I assume it is the stdlib one, and don't want to be confused
by the presence of your own module.

 

[TP]

While the solutions given by others in this thread will work, I think it
is best policy to not name your own modules after stdlib ones. When I see
"os" referenced in code, I assume it is the stdlib one, and don't want to
be confused by the presence of your own module.

Yes, I have finally chosen this alternative: things are much simpler like
this.
Thanks

--
python -c "print ''.join([chr(154 - ord(c)) for c in '*9(9&(18%.\
9&1+,\'Z4(55l4('])"

"When a distinguished but elderly scientist states that something is
possible, he is almost certainly right. When he states that something is
impossible, he is very probably wrong." (first law of AC Clarke)

 

[Carl Banks]

(Could you please set a valid email address for people to contact you
if necessary?)



You will, I think, like the new distinction between “absolute” and
“relative” imports <URL:http://www.python.org/dev/peps/pep-0328/>.

He might, but it won't help him with his problem. Relative imports
aren't involved in this situation.


Carl Banks