> it's pretty clear to me that this is only confusing if you intentionally do you very best to try to add confusing structure around it in an attempt to fool th

> it's pretty clear to me that this is only confusing if you intentionally do you very best to try to add confusing structure around it in an attempt to fool the reader into thinking something very different and weird is going on. This has come up from a Core Developer before [1] so it's not just code golfers having a laugh. Yes, the docs note the tokenization behavior [2], but Guido's response today in the above mail thread is also pretty unambiguous: > I would totally make that a SyntaxError, and backwards compatibility be damned. 1: https://mail.python.org/archives/list/python-dev@python.org/thread/D2WPCITHG2LBQAP7DBTC6CY26WQUBAKP/#D2WPCITHG2LBQAP7DBTC6CY26WQUBAKP https://mail.python.org/archives/list/python-dev@python.org/... 2: https://docs.python.org/3/reference/lexical_analysis.html#whitespace-between-tokens https://docs.python.org/3/reference/lexical_analysis.html#wh...