News for hackers. Stuff that matters.

A comment on Why does `True == False is False` evaluate to False in Python? (2013). Parent comment

Re:Why does `True == False is False` evaluate to False in Py... by collyw on Saturday May 02, 2020 @09:06AM (#23051542)
Would I be correct in avoiding "is" for any simple data types, and only using it for objects?
[ Parent | on HN ]
Re:Why does `True == False is False` evaluate to False in Py... by lonelappde on Saturday May 02, 2020 @09:27AM (#23051654)
Integers are not simple data types in python. https://docs.python.org/2/c-api/int.html#PyInt_FromLong

You'd be correct to use 'is' to mean 'is', and '==' to mean '==', following their definitions.

[ Parent | on HN ]
Re:Why does `True == False is False` evaluate to False in Py... by Scarblac on Saturday May 02, 2020 @10:28AM (#23051976)
It's idiomatic to use it for comparisons with the value `None`, which is a singleton so it's always that one.

Other than that, just don't use `is`.

[ Parent | on HN ]
Re:Why does `True == False is False` evaluate to False in Py... by sbergjohansen on Saturday May 02, 2020 @09:43AM (#23051733)
See the comment by lonelappde, but note that the example under discussion here is actually not about `is` vs. `==` either.
[ Parent | on HN ]