RE: python imports

> This is an idea/suggestion,

> When an import is issued from a chrome page, or a script imported from 
> a chrome page. It should automatically look in the directory of the 
> chrome page first for imports.

The problem with this is that the file will generally be in a .jar file.  As a 
result, a custom importer will need to be written, and there is no opportunity 
to write the .pyc file.

Complicating things is that XUL itself has a "script cache" that stores 
compiled Python code.  It would make sense to me for any such scheme to 
leverage that same cache (thereby avoiding the JAR file in most cases)

I do see exactly what you are trying to do - I'm just not sure of the best way 
to tackle it.  In general, I'd like to ensure we have it (somewhere close to) 
"correct" so we don't need to support too many schemes going forward.

Cheers,

Mark