[issue36617] The rich comparison operators are second class citizens

Change by Mark Dickinson : -- nosy: +mark.dickinson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://m

[issue36617] The rich comparison operators are second class citizens

Eric V. Smith added the comment: I assume the OP is using the stdlib parser module just to show what is a syntax error and what isn't. But most of the characters in the example strings aren't required, so it can be simplified. Here is a simpler case demonstrating what I think the OP is tryin

[issue36617] The rich comparison operators are second class citizens

SilentGhost added the comment: It seems to be parser module. https://docs.python.org/3/library/parser.html#creating-st-objects -- nosy: +SilentGhost ___ Python tracker ___ __

[issue36617] The rich comparison operators are second class citizens

Steven D'Aprano added the comment: Sorry, I don't understand your demonstration. What's the mystery ``parser`` object with an ``expr`` method? What is it doing? Your comment says "all binary/unary number ops work" but I don't know what you mean by "work". Could you show some plain, vanilla P

[issue36617] The rich comparison operators are second class citizens

New submission from Dan Snider : The rich comparison operators have an (far as I can tell, unnecessary) limitation compared to the other binary operators, being that the result of an unparenthesized comparison expression cannot be unpacked using the *iterable "unpack" operator (does that thin