> Alex Martelli wrote: > > >So it can't be global, as it must stay a keyword for backwards > >compatibility at least until 3.0. [David] > Why? Removing keywords should be much simpler than adding them. I > have no idea how hard it is to hack the parser to adjust, but I > can't imagine how having 'global' no longer be a keyword as far as > its concerned break b/w compatibility. > > What am I missing? I don't recall the context, but I think the real issue with removing 'global' is that there's too much code out there that uses the global syntax to remove the global statement before 3.0. --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