Guido van Rossum wrote: > BTW this idea is quite old; I've described it a few years ago under a > subject something like "low-hanging fruit". I really like this idea. If a patch appeared on SF soon, do you think 2.3 could include a warning for code that violates the rule? If so, how about also including a flag to allowed optimizations based on the rule? For example, I think we could have the equivalent of LOAD_FAST for builtin names. Implementing the optimizations could be a bit of work, especially with the existing compiler, but I think the warning should be fairly easy. Neil
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