Best afterTruthiness: what counts as true

and / or / not — and what or returns

Reading x == 1 or 2 as 'x is 1 or 2' is the classic boolean trap. Python groups it as (x == 1) or 2, and or hands back an operand, not always a tidy True/False. Watch what actually lands in match.

Check whether x (which is 5) is equal to 1 or 2.

x == 1 or 2 is always truthy execution-derived · CPython

variables

state after line 1 runs

variable	value
`x`	`5`

step 1 / 2

Click a line, drag the slider, or use the ← → keys.

What you are looking at

Watch match closely — the value may not even be a boolean.

Buggy — match = x == 1 or 2 becomes False or 2, and or returns its first truthy operand: the integer 2. Not True — the number 2, which is truthy, so any if match: would always fire.
Procedural — match = x == 1 or x == 2 compares against both values in full and gives a real False. Each side of an or needs to be a complete condition.

Every state you see came from running the program under CPython's tracer at build time — see how GlassBox stays honest.