That all sounds great!

>  All of that seems a little bit complicated, but it avoids the
>  management of pth files in pyxpcom (I must be crazy).

Can you elaborate here?  A long time ago I went to some pain to allow .pth
files in a local pyxpcom directory to be sniffed, so stuff could be dropped
there and "just work".  The idea is that you might be sharing a Python
between many xulrunner apps, so you need a "local" path in addition to the
"global" Lib/site-packages folder which have .pth files processed.  Indeed,
I can't see a good reason why easy_install/eggs shouldn't "just work"
already from a Python distribution hosting pyxpcom (but I've never tried)

I'm interested to know if you are explicitly trying to *avoid* some of this
behavior, and why?  I would have thought that .pth files working is a
*feature* rather than a liability :)  Or quite possibly I'm not
understanding something...

Cheers,

Mark

_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs