I understand about the registries, at least to the effect that it's a xpcom
component registration issue rather than a python module not found issue.
That makes enough sense.  I simply tried to add entries to my system path,
and launched the interpreter from different locations in the hope that
perhaps my GRE would register the appropriate components... I guess those
paths had more to do with how python locates things, so that was a bit
silly.

The only reason I bring up the mozconfig is in the off chance that there's
anything else (besides xulrunner itself) that I should be building when
starting development.  For example, I was hoping to build firefox with
python support, simply because I've seen several firefox+python integration
examples that I wanted to try out, but for one reason or another (maybe I
set things up wrong, maybe I'm looking at outdated docs) firefox doesn't get
built when I make the source tree, at least not the firefox executable.

In any case!  Thanks for the help.  I *do* have a working xulrunner and was
*totally* unaware that it came with a -console switch that lets me view
things on stdout.  Most helpful!

Cheers,

-R

On 7/5/07, Mark Hammond <mhammond@[...].au>  wrote:
> 
>  > Well again, the XULRunner app works!
> 
>  Yes, and this is all we promise.  Having an interactive Python work is a
>  bonus, but occasionally things get in the way here.
> 
>  > I've added as many conceivable paths to my PYTHONPATH as I can imagine,
>  > as well as started my interactive python shell from a myriad of
>  different
>  > locations with no luck
> 
>  The problem has nothing to do with Python not being able to find its
>  modules, but with mozilla being unable to locate all its registries.
> 
>  > I guess if I stick with it... are there any diagnostic tools I can pick
>  > up to ease my headaches?  Right now I'm limited to taking my one simple
>  > XULrunner example, and sort of permuting it to do different stuff, using
>  > javascript alerts as my primary source of debug statements (bleck!)
> 
>  Why can't you use Python debuggers and/or print statements here
>  (passing -console to the xulrunner executable might help)?  IIUC, you have
>  xulrunner working OK, so you should be able to do anything Python related
>  when running under XULRunner.
> 
>  > I guess even beyond that, does anyone have any suggestions regarding
>  mozconfig
>  > files I can use to build the trunk to give me the appropriate suite of
>  tools
>  > for developing a standalone XUL application? (a la songbird, etc...)  I
>  could
>  > post mine, if that's informative.
> 
>  I'm afraid I'm a little lost now - you have XULRunner working, right?  Why
>  are you looking for a new mozconfig?
> 
>  Cheers,
> 
>  Mark
> 
>