module imports and st_mtime

utils/autoreload.py) Some of the code running under this django server imports simplejson, the C-implemented module of which has been put at /Users/tow/.python- eggs/simplejson-2.0.9-py2.5-macosx-10.5-i386.egg-tmp/simplejson/ _speedups.so This hasn't been touched since it was installed: ls -l ~/.p

Re: module import search path strangeness

On Aug 12, 4:59 pm, Peter Otten <[EMAIL PROTECTED]> wrote: > tow wrote: > > On Aug 12, 9:56 am, Peter Otten <[EMAIL PROTECTED]> wrote: > >> tow wrote: > > >> > Basically, I had thought that import and imp.find_module used exactly > >> > the

Re: module import search path strangeness

On Aug 12, 9:56 am, Peter Otten <[EMAIL PROTECTED]> wrote: > tow wrote: > > Basically, I had thought that import and imp.find_module used exactly > > the same > > search path, but the above example shows that at least in this > > circumstance they > > don&#x

Re: module import search path strangeness

On Aug 12, 4:59 am, "Gabriel Genellina" <[EMAIL PROTECTED]> wrote: > En Mon, 11 Aug 2008 19:19:19 -0300, tow <[EMAIL PROTECTED]>   > escribi : > > > I have a python script (part of a django application, if it makes any > > difference) which is exhib

module import search path strangeness

fail; the directory containing my_module is not in sys.path (though the my_module directory itself is). More puzzlingly, printing out my_module.__file__ gives: /home/tow/test/my_module/../my_module/__init__.pyc I don't really understand what the ".." is doing in there. Can someone expl