[Python-3000] pep 3124 plans

[Jim Jewett]

On 7/17/07, Phillip J. Eby <pje at telecommunity.com> wrote:
> At 02:47 PM 7/17/2007 -0700, Guido van Rossum wrote:
> >I have one remaining question for Phillip: why is your design
> >"absolutely dependent on being able to modify functions in-place"?

> It allows the framework to bootstrap via successive
> approximation.  Initially, the 'implies()' function is just a plain

Would it work to make the original 'implies()' something other than an
ordinary function?  I realize that you prefer being able to overload
anything, but it seems that you *could* mark the ones you'll need to
overload as part of bootstrapping.

> In 2.x, I take advantage of the ability of code run inside a class
> suite to change the enclosing class' __metaclass__; in 3.0,

What was missing from the __class__ attribute that you get from the
super PEP fail?  Was it that you wanted access to the class while
defining the class, before the method is ever called?

Why can't an ordinary class decorator work?  Is it because you want
the funky stuff to be conditional?  If so, is that really required?

Or are you just objecting to the fact that metaclasses like this won't
be the default?

-jJ