[Python-Dev] Re: redefining is

[Andrew Koenig]

> This is why you cannot mess with "is". We replaced all the "== None"
> with "is None" in our code to avoid tracebacks when the __eq__ method
> fails on a None. yes there is a bug in the __eq__ code, but I don't
> want the __eq__ code run at all in almost all cases.

The proposal we're talking about would not change the meaning of
"x is None".  For that matter, it would not change the meaning of "x is y"
for any singleton y.