Created
April 6, 2012 07:42
-
-
Save davisagli/2317969 to your computer and use it in GitHub Desktop.
Marmoset patching
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
import inspect | |
def marmoset_patch(func, s, r): | |
source = inspect.getsource(func).replace(s, r) | |
exec source in func.func_globals | |
func.func_code = func.func_globals[func.__name__].func_code | |
def foo(): | |
print 1 | |
print 2 | |
print 3 | |
foo() | |
# 1 | |
# 2 | |
# 3 | |
marmoset_patch(foo, '3', "'ZOMG'") | |
foo() | |
# 1 | |
# 2 | |
# ZOMG |
@kellerkeller
a monkey patch is when you re-open an object for modification, some languages like ruby allow for this, and it's very common for large ruby apps to build classes out of several files. Python discourages monkey patching as looking through multiple files for where a method is defined gets tired fast, like the first time it happens, and as the Zen of Python tells us, explicit is better than implicit
O M G
Have the python people heard of this?
This technique intrigues me. I look forward to apply it in many real-life scenarios.
This is so wrong, the right solution is to use AST rewriting!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This seems like a good idea. Thank you for helping a new programmer out with learning new techniques. :) More seriously, what is monkey patching?