Jon wrote:
> It appears that (windows) python searches in the current working
> directory before looking in the local site-packages directory, or that
> '.' comes first in sys.path?
Unless it behaves very differently on Windows from
everything else, this isn't quite true. The current
directory is
"Jon" wrote:
> Would somebody please explain how to know what is going on when an
> import statement is ambiguous?
there is no ambiguity: python searches through a list of directories, in a given
order.
the list is stored in the sys.path list, which you can inspect and modify
freely.
also see
It appears that (windows) python searches in the current working
directory before looking in the local site-packages directory, or that
'.' comes first in sys.path? The problem arises when I made the mistake
of running a test program from the same directory where I built and
installed my package. P
