Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #63639

Monkeypatching a staticmethod?

Show all headers | View raw

This is kind of surprising.  I'm running Python 2.7.1.  I've got a class 
with a staticmethod that I want to monkeypatch with a lambda:

----------------------------------
class Foo:
    @staticmethod
    def x():
        return 1

Foo.x = lambda: 2
print Foo.x()
----------------------------------

What's weird is that it seems to remember that x is a staticmethod 
despite having been patched:

Traceback (most recent call last):
  File "static.py", line 8, in <module>
    Foo.x()
TypeError: unbound method <lambda>() must be called with Foo instance as 
first argument (got nothing instead)

What seems to work is to patch it with another staticmethod:

----------------------------------
class Foo:
    @staticmethod
    def x():
        return 1

@staticmethod
def x():
    return 2

Foo.x = x
print Foo.x()
----------------------------------

$ python static.py
2

I didn't even know you could define a staticmethod outside of a class!

I suspect this post is really just my way of admitting that while I've 
used staticmethods plenty, I've never fully understood the details of 
what happens when you construct them :-)

Back to comp.lang.python | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Monkeypatching a staticmethod? Roy Smith <roy@panix.com> - 2014-01-10 00:23 -0500
  Re: Monkeypatching a staticmethod? Ian Kelly <ian.g.kelly@gmail.com> - 2014-01-10 00:31 -0700
    Re: Monkeypatching a staticmethod? Piet van Oostrum <piet@vanoostrum.org> - 2014-01-10 15:04 +0100

csiph-web