Nick Coghlan wrote:The problem with any non-overriding descriptor bound to type is that
> On Thu, May 10, 2012 at 6:11 PM, Mark Shannon <m...@hotpy.org> wrote:
>> Finally, could you remind me how the proposed type.define differs from
>> I can't see any difference (apart from parameter ordering and the extra name
>> parameter in builtins.__build_class__).
> It's the officially supported version of that API - the current
> You'll find there's no mention of __build_class__ in the language or
> (This is explained in the tracker issue and the previous thread that
> I prefer type.define(), but if the descriptor protocol does cause
when accessed as type.define it acts as a descriptor, but when accessed
from any other class, say int.define it acts as a non-overriding
meta-descriptor; c.f. type.mro() vs int.mro()
To avoid this problem, type.define needs to be an overriding descriptor
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.