Re: [Pyobjc-dev] unbound methods

[Jack J. <Jac...@cw...>]

My preference for the implementation of the various "magic" bits for 
accessing class methods, unbound instance methods, etc. would be to use 
methods and class methods (Python methods and Python class methods) on 
the ancestor of all objects (the NSObject bridge object?).

This would give us class.pyobjc_getClassMethod("pythonicname"), 
class.pyobjc_getUnboundMethod("pythonicname") and  
instance.pyobjc_getBoundMethod("pythonicname"). Aside from attribute 
access and such, instance.pyobjc_getBoundMethod("pythonicname") should 
be equivalent to instance.pythonicname. class.pythonicname would become 
equivalent to
try:
	return instance.pyobjc_getClassMethod("pythonicname")
except AttributeError:
	return instance.pyobjc_getUnboundMethod("pythonicname")

Or, if we add a second "default" parameter to all the _get methods,
     return instance.pyobjc_getClassMethod("pythonicname", None) or 
instance.pyobjc_getUnboundMethod("pythonicname")
--
Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman