On Aug 29, 2019, at 15:28, Guido van Rossum <[email protected]> wrote: > > A wart will be that we can make `int | None` work but we shouldn't make `None > | int` work (I don't want to add any new operator overloads to `None`, it > should always be an error).
Is there a reason that type.__ror__ wouldn’t handle that, something funky about type, or about builtin types in general, that I’m forgetting? _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/V42PNUZOIV2NGY7QX47BDPTXQCQ2EQU7/ Code of Conduct: http://python.org/psf/codeofconduct/
