> Note too that we can't change the generated code at all for 2.3 unless under > the control of a new future statement, else existing None-abusing code could > break. I'm trying to eat the cake and have it too, by detecting if None is being abused and disabling the change of LOAD_GLOBAL to LOAD_CONST. If it works (and probably will), we may then choose to include warnings, keep it that way forever, or whatever. -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ]
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