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 mark.dickinson
Recipients amaury.forgeotdarc, mark.dickinson, rhettinger, skrah, terry.reedy
Date 2010-11-19.11:12:17
SpamBayes Score 2.2091217e-05
Marked as misclassified No
Message-id <1290165139.77.0.707431544334.issue10356@psf.upfronthosting.co.za>
In-reply-to
Content
[Stefan]
> ... a direct request to raise an exception...

Understood;  the issue is that this conflicts with the general expectation that equality (and inequality) comparisons always work (at least, for objects that are perceived as immutable).  I think there needs to be a very good reason to have an equality comparison raise an exception, and I don't find this particular reason good enough.  The expected IEEE 754 semantics are still available through the published API:  e.g., using Decimal.compare instead of '=='.

So I'd lean towards having '==' follow Python rules rather than IEEE 754 rules in this case, with Decimal.compare available for the times when the IEEE 754 rules are important.
History
Date User Action Args
2010-11-19 11:12:19mark.dickinsonsetrecipients: + mark.dickinson, rhettinger, terry.reedy, amaury.forgeotdarc, skrah
2010-11-19 11:12:19mark.dickinsonsetmessageid: <1290165139.77.0.707431544334.issue10356@psf.upfronthosting.co.za>
2010-11-19 11:12:17mark.dickinsonlinkissue10356 messages
2010-11-19 11:12:17mark.dickinsoncreate