[Python-Dev] Adding types.build_class for 3.3 (original) (raw)
Nick Coghlan ncoghlan at gmail.com
Thu May 10 12:19:58 CEST 2012
- Previous message: [Python-Dev] Adding types.build_class for 3.3
- Next message: [Python-Dev] Adding types.build_class for 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, May 10, 2012 at 7:51 PM, Mark Shannon <mark at hotpy.org> wrote:
To avoid this problem, type.define needs to be an overriding descriptor such as a property (a PyGetSetDef in C). Alternatively, just make 'define' a non-descriptor. It would unusual (unique?) to have a builtin-function (rather than a method-descriptor) bound to a class, but I can't see any fundamental reason not to.
Oh, I see what you mean now. I hadn't fully thought through the implications of the static method being accessible through all instances of type, and that really doesn't seem like a good outcome. Exposing it through the types module as an ordinary builtin function is starting to sound a lot more attractive at this point.
Cheers, Nick.
-- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
- Previous message: [Python-Dev] Adding types.build_class for 3.3
- Next message: [Python-Dev] Adding types.build_class for 3.3
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]