Raymond Hettinger <[EMAIL PROTECTED]> added the comment: I'll take up the doc fix for the current state of affairs.
A change from returning NotImplemented to raising NotImplementedError would need be a separate feature request or PEP. Alternatively, we could decide to allow decimal/float comparisons -- the float can be converted to a decimal exactly and compared exactly -- it would be slow but it would work and have precise semantics. Am resetting the priority back to low because the current behavior is exactly what is supposed to happen. It is an automatic consequence of how we use NotImplemented and the decision to allow integer/float and integer/decimal comparisons but not float/decimal comparisons. There is not bug here, just something that offends ones sensibilities. ---------- assignee: -> rhettinger priority: normal -> low _______________________________________ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4087> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
