That's interesting. The code that resolves the filename looks through
sys.path, trying to find the files, so presumably it would find it if your
sys.path referenced the top directory of Webware, or contains '' for the
current directory which Launch.py makes the top directory in webware. Then
the relative paths will work.
Is there a chance that something is changing the current directory before
printing the errors? That could prevent it from finding the sources. But
if it can't find the sources relative to the path, then it probably can't
find them to import either.
> -----Original Message-----
> From: Tripp Lilley [mailto:tlilley@...]
> Sent: Tuesday, November 26, 2002 9:28 PM
> To: webware-devel@...
> Subject: [Webware-devel] install.py bugfix
> I don't have a current CVS head (and don't have disk space to grab one
> right now), otherwise I'd put this in myself. I've browsed
> the CVS head,
> though, and the bug remains:
> compileall.compile_dir(".", 10, '', 1)
> should be:
> compileall.compile_dir(os.path.abspath("."), 10, '', 1)
> Otherwise, python generates .pyc files with relative paths to
> the source
> files, and then WebKit can't find them when it prints a stack
> trace. You
> end up with lines that have things like
> line 142, lookupAttr", but without the extracted source.
> This SF.net email is sponsored by: Get the new Palm Tungsten T
> handheld. Power & Color in a compact size!
> Webware-devel mailing list