On Tue, 8 Jan 2008 20:40:43 -0500, "Jason Persampieri"
> I've switched over to the standalone web-server and was still seeing this
> problem. It was especially prevalent when dynamically deciding between
> importing "foo/lib.py" and "bar/lib.py". Of course, since you have to
> the sys.path to do either, this behavior is expected. I worked around it
> including "del sys.modules['lib']" just before my import line.
Hmm, Spyce trackes modules by the full path to the .pyc, so that
shouldn't be a problem. If you can come up with a reproducible test
case I'd be happy to dig further. (The code responsible for this is