Stefan Krah added the comment: My apologies if that wasn't clear: "fine grained" refers to the exception messages. A function can raise InvalidOperation for different reasons.
decimal.py gives a specific error message in each case. libmpdec just signals the standard conforming InvalidOperation. The relevant passage from the standard is here: http://speleotrove.com/decimal/daops.html#refremain "This operation will fail under the same conditions as integer division." decimal.py, decNumber and libmpdec all do the same thing, so there is no libmpdec issue other than that the error *messages* could be improved. I fully understand if you find the behavior surprising (after all the remainder fits in the precision), but as long as we follow the standard we can't change that. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue21227> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
