I think there's a few in there. But most people aren't going to write code that way. It's good to know, and keep in your head, but if you have to think too hard in the future if a piece of code is correct, it's probably better to rewrite it anyway. And weird code like that shows up like a sore thumb in reviews.

> Is anyone surprised by `(1 > 0) < 1`?

This is presumably meant as a setup for the fact that the result of `1 > 0 < 1` differs from the result with parentheses set up either way (because this is a chained comparison), and furthermore that such chained comparisons are legal even when they don't have the operators all "pointing" the same way (like in mathematical notation). And that operators like `in` and `is` are allowed to participate in this system on equal footing.

> Java as contrast has interning wtfs because == between java objects does essentioally what python's `is` does.

It's pretty sensible because i wouldn't expect that operator to call a method - since Java does not have operator overloading.

Yeah, it's not that bad, but `if foo == "bar"` or `foo == Integer(someInt)` looks reasonable, and worse, sometimes works