Message390981
Came across this riddle today:
>>> [0x_for x in (1, 2, 3)]
[15]
Initially I thought this was related to PEP 515 but the unexpected behavior extends to simpler examples as well, such as:
>>> x = 5
>>> 123or x
123
>>> 123and x
5
I'm not familiar enough with C to understand why this is being parsed/tokenized this way, but this seems like it should instead be a SyntaxError. This appears to be fairly old behavior, as the non-underscored version works back to at least 2.7.
And a bonus:
>>> 0x1decade or more
31378142 |
|
Date |
User |
Action |
Args |
2021-04-13 18:27:19 | sco1 | set | recipients:
+ sco1 |
2021-04-13 18:27:19 | sco1 | set | messageid: <1618338439.83.0.0166317758112.issue43833@roundup.psfhosted.org> |
2021-04-13 18:27:19 | sco1 | link | issue43833 messages |
2021-04-13 18:27:19 | sco1 | create | |
|