Re: [Jython-dev] Metaclasses, _doget, and ExtensionClasses

[Phillip J. E. <pj...@te...>]

At 11:29 AM 7/15/01 +0000, Finn Bock wrote:
>[Samuele]
>
> >[a patch]
> >plus an empty org.python.util.PyMetaClass interface
> >could make into the code, no problem with that.
> >
> >I can play the good guy <wink> and if it's OK for Finn, it can be committed.
>
>I haven't tested it, but if Samuele's patch would work for you Phillip,
>then I see no problem in adding it. But ...

Let me play with it today.  I think it needs to be repositioned from an 
else to the first if() in order to work properly.



> >The whole point is that the patch will last until 2.2 and maybe survive to
> >that.
>
>Exactly! If this change turns out to interact poorly with the up-comming
>2.2 "descr" change it might be removed again. So for the moment the
>PyMetaClass hook should be considered an experimental feature.
>
>OTOH, if you can deliver an ExtensionClass compatible module, then it is
>an excellent argument in favor of keeping the proposed PyMetaClass hook.

My initial goal is just to provide an emulation of ExtensionClass' 
MethodObject and ComputedAttribute classes for use with TransWarp.  But as 
time permits I'd like to experiment with replicating EC's Acquisition and 
Persistent modules.  I'll be happy to release anything I do under 
Jython-compatible licensing.