SnoopJThis is your periodic reminder that `0xfor....real` is a syntactically-valid AND error-free #Python program
Wattana's Place of Brainrot@SnoopJ how does that get past the parser? And how does it work?
@Atirut it lexes the same as: `0xf or ....real` and the first part of the boolean OR is truthy, so short-circuit returns 15 without ever evaluating the RHS which would lead to an `AttributeError` if evaluated
@SnoopJ ahhhh, I think that's what happens when the lexing logic is "consume until no hex characters" and not "consume until no hex characters AND check if it's a proper token boundary".