summaryrefslogtreecommitdiffstats
path: root/Lib/test/badsyntax_future4.py
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>2001-09-28 23:49:48 (GMT)
committerGuido van Rossum <guido@python.org>2001-09-28 23:49:48 (GMT)
commit4bb1e36eec19b30f2e582fceffa250e1598262e1 (patch)
tree0ba999260cfc7eaa6f9ce6a7e9f251d79edcf1e7 /Lib/test/badsyntax_future4.py
parent9bea3abf0d7c658a95a92a295c82d5bf0b583f08 (diff)
downloadcpython-4bb1e36eec19b30f2e582fceffa250e1598262e1.zip
cpython-4bb1e36eec19b30f2e582fceffa250e1598262e1.tar.gz
cpython-4bb1e36eec19b30f2e582fceffa250e1598262e1.tar.bz2
It's a fact: for binary operators, *under certain circumstances*,
__rop__ now takes precendence over __op__. Those circumstances are: - Both arguments are new-style classes - Both arguments are new-style numbers - Their implementation slots for tp_op differ - Their types differ - The right argument's type is a subtype of the left argument's type Also did this for the ternary operator (pow) -- only the binary case is dealt with properly though, since __rpow__ is not supported anyway.
Diffstat (limited to 'Lib/test/badsyntax_future4.py')
0 files changed, 0 insertions, 0 deletions