Hello,

Some comments on the PyXPCOM extension:

Std modules seem to be missing from the python shipped with the
extension (I missed the md5module (_md5) which is needed by md5.py).

To try and fix the above, I tried to build the extension myself on
a linux ubuntu 7.10 workstation.
In build/build_pyxpcom_ext.sh, Python was failing at make install due to
PYTHONHOME being set, I moved the 'export PYTHONHOME' part after the
make install and that fixed it. I don't know if that is specific to
linux or ubuntu or my comp...

The disutils module complained about config/Makefile not being
available, I added it to build/package_pyxpcom_ext.py.
This, I believe, should be available by default (I don't dare to send a
patch cause I kinda botch the script to get my ways. Todd, if you want a
clean diff, drop me a mail).


A non-release:

I'm pleased to announce PyEgg-0.1.0, a setuptools wrapper extension for
the PyXPCOM extension.

PyEgg allows you to install/[up/down]grade/remove python eggs that will
be available to your PyXPCOM enabled xulrunner application.

A non-release because it is experimental, and I have no place to put it
on the internet (I attached it to this mail but I don't know if the
list allows zipped attachment, in case it's not here, interested people
should drop me a mail, I'd be glad to send it (it's only 14KB)).

You need PyXPCOM fixed as described in the comments above, and
xulrunner-1.9.
Once you have a xulrunner app working with pyxpcom you need to drop the
unzipped extension in your extensions folder.
To use it open the extension manager (for details on how to do that:
http://developer.mozilla.org/en/docs/XULRunner_tips#Extension_Manager)
and click on PyEgg preferences.
The ui is, unfortunately, really basic (some would say rough), it
allows you to manage local eggs/source packages and PyPi packages.
Tip: if you want to see what happens when setuptools is called, open
the PyEgg console (really useful when installing PyPi packages).
Then, in your other extensions in modules/scripts that would be in the
pylib folder you can do import package-name, where package-name is the
name of a package installed with PyEgg.
All of that seems a little bit complicated, but it avoids the
management of pth files in pyxpcom (I must be crazy).


hope it helps

lekma