> IIRC the largest expense in function calls is setting up the frame > object for the new function to use. I don't think there are any > low-hanging fruit here, because the frame model is pretty deeply > embedded in the interpreter. It seems like all the work in > PyEval_EvalCodeEx() has to get done sometime. Then that's where we should have a clean fresh look. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4