> In that case there's really no point to changing the grammar now either, > right? This is a context-sensitive warning. In that case, I'd like us to > start warning about (at least) "non-expression" uses of 'True' and 'False' > too. That is, if we can't change the generated code yet anyway, we may as > well start warning about everything we *intend* to make keywords someday. > The same context-senstive checks are needed for each such name. Good point. Same question. Any takers? --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