[issue43833] Unexpected Parsing of Numeric Literals Concatenated with Boolean Operators

[Shreyan Avigyan]

Shreyan Avigyan <shreyan.avigyan at gmail.com> added the comment:

Hi. I just want to know why is and, or operators behaving like this. The behavior is described in https://bugs.python.org/issue43833#msg390996. Moreover I researched a little more and found out even if __and__, __or__ methods are defined the and, or operators doesn't seem to work. As Serhiy described in https://bugs.python.org/issue43833#msg390998 the parser reads [0x1for x in (1,2)] as [0x1f or x in (1,2)] which is the parser's fault but why is the or operator behaving like that?

----------

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue43833>
_______________________________________