PYTHONPATH and module names

Tobiah tshepard at
Mon Jul 1 20:29:35 CEST 2013

So today, I created a file called '',
and my program broke.  It turned out that I was
also import 'gluon' from web2py, which in turn,
somewhere, imported the regular python
with which I was not familiar.

So the question is: Does one simply always have
to be knowledgeable about existing python library
names, or is having '.' in the python path just
a bad idea?  Is there a way, not having '.' in
the path to explicitly specify the current directory?
Something analogous to import ./foo ?



More information about the Python-list mailing list