If Decimal objects prematurely throw a TypeError before trying the __rop__, is Decimal broken, or was it designed this way?
I suspect the former, since I can't recall this subject coming up at any point during the PEP approval or implementation process. And I was one of the people who worked on it before 2.4 was released :)
So I'd suggest:
a) Checking that replacing the relevant "raise TypeError" calls in Lib/Decimal.py with "return NotImplemented" gives you friendlier behaviour.
b) Filing a bug report on SF
I'll be bringing the question up on py-dev as well.
Cheers, Nick.
--
Nick Coghlan | [EMAIL PROTECTED] | Brisbane, Australia
---------------------------------------------------------------
http://boredomandlaziness.skystorm.net
--
http://mail.python.org/mailman/listinfo/python-list
