This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients facundobatista, georg.brandl, mark.dickinson, rhettinger, terry.reedy
Date 2008-10-10.00:20:05
SpamBayes Score 3.8123676e-07
Marked as misclassified No
Message-id <1223598011.03.0.930891117446.issue4087@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2008-10-10 00:20:11rhettingersetrecipients: + rhettinger, georg.brandl, terry.reedy, facundobatista, mark.dickinson
2008-10-10 00:20:11rhettingersetmessageid: <1223598011.03.0.930891117446.issue4087@psf.upfronthosting.co.za>
2008-10-10 00:20:07rhettingerlinkissue4087 messages
2008-10-10 00:20:05rhettingercreate