Why does `True == False is False` evaluate to False in Python? (2013)

Re:Why does `True == False is False` evaluate to False in Py... by ramshorns on Saturday May 02, 2020 @12:00AM (#23049049)

This is a bit like something you can do in C, almost by accident as a bonus language feature.

  x = y = z = 4;

But I think this is assignment expressions which were controversial in Python or something.

[ Parent | on HN ]

Re:Why does `True == False is False` evaluate to False in Py... by sk0g on Saturday May 02, 2020 @12:23AM (#23049169)

Yeah in Python you can do, say, a = b = []

But then the two lists are the same, and appending to one appends to the other. Not particularly useful.

[ Parent | on HN ]

Re:Why does `True == False is False` evaluate to False in Py... by Ragib_Zaman on Saturday May 02, 2020 @05:34AM (#23050561)

It's useful when the object being assigned to those variables are literals instead of reference types, which in my experience is most of the time when you want to do the simultaneous assignment. When you do want to do reference types, you can do a,b = [], [].

[ Parent | on HN ]

Re:Why does `True == False is False` evaluate to False in Py... by mark-r on Saturday May 02, 2020 @12:21AM (#23049160)

Not anymore, check out the walrus operator.

[ Parent | on HN ]