[Python-Dev] lament for the demise of unbound methods (original) (raw)
Benjamin Peterson benjamin at python.org
Thu Jul 4 21:50:09 CEST 2013
- Previous message: [Python-Dev] lament for the demise of unbound methods
- Next message: [Python-Dev] lament for the demise of unbound methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2013/7/4 Eric Snow <ericsnowcurrently at gmail.com>:
On Thu, Jul 4, 2013 at 5:21 AM, Chris Withers <chris at simplistix.co.uk> wrote:
Hi All, In Python 2, I can figure out whether I have a method or a function, and, more importantly, for an unbound method, I can figure out what class the method belongs to: >>> class MyClass(object): ... def method(self): pass ... >>> MyClass.method >>> MyClass.method.imclass <class '_main_.MyClass'> There doesn't appear to be any way in Python 3 to do this, which is a little surprising and frustrating... What am I missing here? You could always monkeypatch builtins.buildclass to add an attribute to every "unbound method" pointing to the class.
I would not reccomend that. build_class is very internal and it's contract may change between versions.
-- Regards, Benjamin
- Previous message: [Python-Dev] lament for the demise of unbound methods
- Next message: [Python-Dev] lament for the demise of unbound methods
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]