News for hackers. Stuff that matters.
Re:In Python, `[0xfor x in (1, 2, 3)]` returns `[15]` by css on Wednesday April 14, 2021 @10:52AM (#26807923)
The check whether a token is a number happens before the check whether a token is a name, as evinced by both the source code and a trivial debugger session.

You are conflating the fact that there is an order to the rules with a strawman that the rules _must_ be evaluated in a specific order. All of the quotes you pulled are facts (Python checks if a token is a number before it checks if it is a name, Python checks if a token is a literal before it checks if it is a name, and the rules are not evaluated concurrently), but your strawman is making a different claim.

Re:In Python, `[0xfor x in (1, 2, 3)]` returns `[15]` by tom_mellior on Wednesday April 14, 2021 @12:57PM (#26809801)
> a strawman that the rules _must_ be evaluated in a specific order.

I'm not the one who wrote "literals have to be evaluated before names".

> rules are not evaluated concurrently

Strawman yourself. I didn't say they were evaluated concurrently, I said that your claim that they can't be evaluated concurrently was wrong. They could be, because they are disjoint, and regardless of order only one of them can match at input starting with a '0' character.

Anyway, I'm done here.