> (And is it time to make assignments to True and False trigger a > SyntaxWarning, or should that wait until 2.5?) We should be much more conservative with that. There's tons of code out there that assigns these (conditionally, if it's 2.3-aware) to truth values and we don't want to break that. The situation with None is much better, since it was always there; AFAIK only a few speed freaks in Zope-land have ever assigned to it (and always using the form "None = None"). --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