This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author shreyanavigyan
Recipients Anthony Sottile, Carl.Friedrich.Bolz, alimuldal, nedbat, pablogsal, rrauenza, sco1, serhiy.storchaka, shreyanavigyan
Date 2021-04-14.08:09:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1618387766.76.0.0690901147133.issue43833@roundup.psfhosted.org>
In-reply-to
Content
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?
History
Date User Action Args
2021-04-14 08:09:26shreyanavigyansetrecipients: + shreyanavigyan, Carl.Friedrich.Bolz, nedbat, serhiy.storchaka, Anthony Sottile, pablogsal, sco1, alimuldal, rrauenza
2021-04-14 08:09:26shreyanavigyansetmessageid: <1618387766.76.0.0690901147133.issue43833@roundup.psfhosted.org>
2021-04-14 08:09:26shreyanavigyanlinkissue43833 messages
2021-04-14 08:09:26shreyanavigyancreate