Re: [Jython-dev] Jython 2.1a3 on j2sdk1.4.0beta

[Jeremy H. <je...@zo...>]

>>>>> "TB" == Titus Brown <ti...@ca...> writes:

  TB> that Zope's C code is primarily in the area of medusa, their
  TB> request-handling front-end.  So, if you can figure out how to
  TB> disentangle Zope from medusa, it shouldn't be too hard to whip
  TB> up something that works.

There is little or no C code in medusa.  A quick scan of the Zope
source tree shows that C code is used in the following places:

    - ExtensionClass and friends, which are used to implement
      acquisition and a host of other things;

    - BTrees, which are used to implement catalogs aka searches; and

    - ZODB, which provides the persistence / transaction machinery.

There is also C code in access control, document templates, and the
PCGI wrapper.  Zope also includes zlib and expat, which are
implemented in C.

In other words, C code provides several crucial features to Zope that
have nothing to do with the front-end.

The recent type-class unification work aims to extend the Python code
so that some (much?) of this C code is unnecessary, but I don't know
how long it will take to see that work folded back into Jython.

  -> Isn't that what they said about the feasibility of implementing
  -> JPython, too?

I recall Guido dismissing it as impossible, too.

  TB> Also see my "Zope is Evil" page for mild commentary about the
  TB> smugness of Zopatistas ;).

I'm sure you have plenty of legitimate technical criticisms of Zope.
"Evil" doesn't suggest to me what they are.  It sounds more like name
calling to me, but perhaps I'm just smug.

Jeremy