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 facundobatista
Recipients facundobatista, georg.brandl, mark.dickinson, rhettinger, terry.reedy
Date 2008-10-10.12:21:19
SpamBayes Score 3.7658065e-06
Marked as misclassified No
Message-id <1223641340.41.0.196539272218.issue4087@psf.upfronthosting.co.za>
In-reply-to
Content
2008/10/9 Raymond Hettinger <report@bugs.python.org>:

> 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.

-0

Note that this could lead to surprising behaviours, when doing these
comparations... Decimal("1.1")==1.1 will be true, buy maybe
Decimal("1.235445687")==1.235445687 will not (I didn't try if this
particular comparison will fail, but hope you get the idea).

This is why I suggested the other way... we now allow comparison to
integers, let's allow comparisons when the floats are equal to the
integers, and no more.
History
Date User Action Args
2008-10-10 12:22:20facundobatistasetrecipients: + facundobatista, georg.brandl, rhettinger, terry.reedy, mark.dickinson
2008-10-10 12:22:20facundobatistasetmessageid: <1223641340.41.0.196539272218.issue4087@psf.upfronthosting.co.za>
2008-10-10 12:21:20facundobatistalinkissue4087 messages
2008-10-10 12:21:19facundobatistacreate