> Therefore, the proposal is to change the definition of "is" as > follows: I completely fail to see what the problem is that this is purporting to solve. You don't use 'is' to compare integers, unless for some very special reason you care whether they're actually the same object. Most of the time you don't care, so you use '=='. The "anomalies" you mention are only a problem in the minds of newbies who haven't actually used Python very much, as far as I can see. > Is this idea worth considering? If not, why not? IMO, it's not worth considering, because its utility is zero considering the way Python is used in practice. Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | A citizen of NewZealandCorp, a | Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | greg at cosc.canterbury.ac.nz +--------------------------------------+
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