Monkey-patching is the technique of swapping functions or methods with others in order to change a module, library or class behavior.
There are some people with strong opinions about it. I haven’t, but it comes really useful when testing, to simulate side-effecting functions or to silence expected errors and warnings.
Class methods monkey patching in Python is really easy, as you can freely assign function to class method names:
1 2 3 4 5 6 7 8 9 10 11
This way all the instances of the target class will have the method monkey-patched and there is no problem with arguments, bindings… Everything really straight-forward.
We can also call the old existing method, to handle only some cases or to add some functionality while not repeating code (DRY):
1 2 3 4 5 6 7 8 9 10 11 12 13 14
But what if we wanted to do the same, patching just a single instance?
To recap, the requirements are:
- we want just the current instance to be patched;
- we want to build something on top of the existing method, not to replace it entirely;
- we want each monkey-patch not to rollback all the previous ones (so no
super()or class method call);
- we want to be able to do so also from inside a method.
The trick is to save and use the existing method as we did above, and then bind the new function to the instance with
types.MethodType before assigning it to the method name.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
And here we go!
A practical example
The monkey-patching of the instance is done on itself by a method of a testing subclass of the downloader.