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

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

At 03:42 AM 7/15/01 +0200, Samuele Pedroni wrote:

>So after the trouble of  a few posts and of making me propose a bad and not
>working hack, you came out
>with some actual code <wink>.
>
> > Nonetheless, I understand that some things just can't or don't make it into
> > a project, for whatever reasons.
>The situation is as follow: in principle the following patch along the line of
>your code

I'll give it a shot.  I think the PyMetaClass check needs to occur *before* 
the PyClass check, though, since the idea is to extend PyClass - if I were 
going to copy all of PyClass' code into PyExtClass, I wouldn't need the 
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.

Fantastic.  I'll see what I can do with it today, and then submit a working 
patch.


>The whole point is that the patch will last until 2.2 and maybe survive to
>that.
>But I'm not willing to commit on the actual internals design or the patch as
>something here to stay.
>The internals after 2.2 are something that should be designed to stay, that's
>my goal.
>E.g. the last PyJavaClasses related bug I had to solve I should resort to an
>hack because
>of the internals... this should be fixed (clearly not an easy thing, perfectly
>aware of that).
>
>So if you will not call me a bad guy <wink> if what you build on top of 2.1
>internals will no longer work with 2.2,
>I think you can have the feature. Not really a technical point, more a
>"political" one, but not a personal ...

I understand.  As of 2.2, I'm sure CPython ExtensionClasses will be getting 
some redesigning also.