> Indeed. Of course, object() is mutable, so there is no proposal to change > the meaning of this program. What I'm concerned about is someone trying to > do the same thing this way: > > missing = 'missing' > > if d.get('somekey', missing) is 'missing': > # it ain't there > > This code contains a bug, but on an implementation that interns strings that > happen to look like identifiers, no test will detect the bug. I'm ready to pronounce. The code is buggy. There are good reasons to keep 'is' the way it always was. The definition of 'is' ain't gonna change. So be it. --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