Barry> ... or setting open() to some debugging func.
Barry> I wouldn't want to completely disallow these, but I'd be happy if
Barry> you had to do something special and/or (more) explicit to make
Barry> them work.
Like a compiler flag to disable the run-time optimization so your debugging
open() would be seen everywhere?
Sort of like Guido's observation about __fastbuiltins__ = True, the frequent
case (regular, optimized version of open()) should be the default, while the
exception requires programmer or user action.
Skip
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