monkeypatching

Quickie here that needs more domain expertise on pymongo than I have right now: Are the "right" parts of the pymongo driver written in python for me to call gevent monkey_patch() and successfully alter pymongo's blocking behavior on r/w within gevent "asynchronous" greenlets? If this will require a little more leg work on gevent and pymongo -- but it is feasible -- I would be more than willing to put in the time as long as i can get a little guidance over irc. Thanks! Note: At small scale mongo writes are not a big problem because we are just queuing a write "request" before unblocking. BUT

Is it at all possible to monkey patch the value of a @property of an instance of a class that I do not control? class Foo: @property def bar(self): return here().be['dragons'] f = Foo() print(f.bar) # baz f.bar = 42 # MAGIC! print(f.bar) # 42 Obviously the above would produce an error when trying to assign to f.bar . Is # MAGIC! possible in any way? The implementation details of the @property are a black box and not indirectly monkey-patchable. The entire method call needs to be replaced. It needs to affect a single instance only (class-level patching is okay if inevitable, but the changed

I'm using a swc from the Axiis project to display visualizations in a project I'm working on. I've run into a bug where re-compiling the library swc would be an easy solution, but I can only use the buggy version of the swc. I have the Axiis source and compiled a version with the bug fixed, though I'm not allowed to use it because of client version restrictions. Does anyone know how I can use the updated Actionscript class/file in my code so it overrides the swc class? I'm not sure if you are allowed to do the following: put the class with your fix in the source path of your main application.

MyClass is defined in module.py . There is no way we can modify it. But we do know the Class definition looks like this: class MyClass: def method(self, msg): print 'from method:', msg I start my script with importing the module and then declaring an object's instance: import module foo = module.MyClass() Then I write my own function: def function(msg): print 'from function:', msg Now, every time foo.method('') is used I want to call function() so it prints the same message too. Would this situation be referred as the monkey patching ? How to achieve what is needed? Yes, it's called monkey

I want to monkey patch on f(*args, **kwargs) from an installed module. I use the idea of decorator on my own code, but other methods from the installed module fails to call f correctly. Here is an example: import numpy as np def log(func): def wrapper(*args, **kwargs): print('logging') return func(*args, **kwargs) return wrapper if __name__ == "__main__": a1 = np.asarray([0, 1, 2]) print(f'a1={a1}') a2 = np.array([0, 1, 2]) print(f'a2={a2}') np.array = log(np.array) a3 = np.asarray([0, 1, 2]) print(f'a3={a3}') a4 = np.array([0, 1, 2]) print(f'a4={a4}') The output is: a1=[0 1 2] a2=[0 1 2] a3=

I have several objects of different kinds (different function names, different signatures) and I monkey patch them to have a common way to access them from different functions. Briefly, there is a dispatcher that takes the objects that I want to patch and depending on the object type it calls different patcher. A patcher will add methods to the object: def patcher_of_some_type(object): def target(self, value): # do something and call self methods object.target = types.MethodType(target, object) # many more of these As the program grows more complicated making a wrapper around the object (or