Re: [pyxpcom] Python Mozilla extension (pyxpcomext) updated
by Atul Varma other posts by this author
Jun 17 2008 6:08AM messages near this date
view in the new Beta List Site
Re: [pyxpcom] Python Mozilla extension (pyxpcomext) updated
|
Re: [pyxpcom] Python Mozilla extension (pyxpcomext) updated
Well, one of the things I noticed a few weeks ago when creating my own
SConstruct file for pyxpcom (using the Python-based SCons build tool) was
that everything needed to build, save for a few header files, is contained
in the nightly builds of the XULRunner SDK:
http://developer.mozilla.org/en/docs/Gecko_SDK
The nice thing about this is that you don't need to compile all of Mozilla
just to make the PyXPCOM binaries.
Mark, I wasn't at your keynote at Pycon, but a friend of mine was and he
mentioned you saying that one of the difficult things about PyXPCOM over the
years is that the Mozilla community thinks PyXPCOM is the Python community's
business, and the Python community thnks it's Mozilla's business. If
Mozilla thinks that PyXPCOM isn't "theirs", then why not move it out of
mozilla-central and into a separate repository where the PyXPCOM community
has full control over it? We could decouple its build system from
Mozilla's, making it easier to understand and change (albeit more fragile
too, but it could be worth the tradeoff if it means more participation and
maintainability). We could even set up a simple buildbot system to
automatically create and test PyXPCOM builds with the latest nightly
XULRunner SDK to be notified of breakages as soon as they happen.
- Atul
On Tue, Jun 17, 2008 at 12:00 AM, Mark Hammond <mhammond@[...].au>
wrote:
> Hi Todd,
> These new releases look great! I'm wondering what you intend to do re
> getting these patches into CVS/Mercurial? I'm slightly concerned that as
> time moves on, the "pyxpcom source code in the Mozilla tree" and the
> "pyxpcom binaries" will diverge in non-trivial ways, ultimately causing
> confusion for users. Further, if you include a patch that we ultimately
> decide is inappropriate to be checked into the pyxpcom source tree, we may
> end up in the position where you are forced to make a fork of pyxpcom just
> to retain backwards compatibility with your other releases.
>
> Do you (or anyone!) have any thoughts on this?
>
> Thanks,
>
> Mark.
>
> > -----Original Message-----
> > From: pyxpcom-bounces@[...].com [mailto:pyxpcom-
> > bounces@[...].com] On Behalf Of Todd Whiteman
> > Sent: Tuesday, 17 June 2008 4:26 PM
> > To: pyxpcom@[...].com
> > Subject: [pyxpcom] Python Mozilla extension (pyxpcomext) updated
> >
> > Hello all,
> >
> > I've updated the Python extension for Mozilla 1.9 builds with the
> > following changes:
> > * now includes PyDOM
> > * windows, Mac OS X and Linux builds available
> > * updated Linux Python builds to use static libraries (fixes problem of
> > missing modules like "ssl", "hashlib")
> > * moved pyxpcom environment setup into a pybootloader stub module
> >
> > Downloads are available here:
> > https://www.mozdev.org/projects/overview/pyxpcomext/
> >
> > The PythonExt build will work in Firefox 3, Songbird and XulRunner 1.9
> > apps.
> >
> > Thanks to Malek (lekma) for reworking the build scripts and bootloader
> > handling.
> >
> > Cheers,
> > Todd
> >
> > _______________________________________________
> > pyxpcom mailing list
> > pyxpcom@[...].com
> > To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
> _______________________________________________
> pyxpcom mailing list
> pyxpcom@[...].com
> To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
>
Thread:
Todd Whiteman
Mark Hammond
Todd Whiteman
Lekma
Mark Hammond
Mark Hammond
Atul Varma
Mark Hammond
Atul Varma
Mark Hammond
|