I am not going to pretend to understand what people such as Ben and Bobby are thinking (they appear to be confusing the difficulty of javascript bindings versus lazy python bindings). However, I am inferring from their replies that they never had and still don't want anything to do with pyxpcom (see https://groups.google.com/forum/#!topic/mozilla.dev.embedding/c_NMcO-N8wo/discussion), and the responsibility of pyxpcom is entirely in the hands of the pyxpcom maintainers.
Although that may be sufficient for pyxpcom, given the notes above, we still have the issue regarding Hulahop. This somewhat confuses me as a google search for hulahop brings me to an OLPC wiki that defines hulahop as "HulaHop is Gecko 1.9 (Firefox 3.0 core) web browser as a simple embeddable control with Python DOM access. It is a PyGTK Widget that you can use in your application to embed a web browser." Therefore is the issue the unwillingness to support hulahop or its successor in newer versions of the Firefox core code or an unwillingness to support pyxpcom or both?
