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 skip.montanaro
Recipients christian.heimes, gvanrossum, nascheme, noam, rhettinger, skip.montanaro, tim.peters
Date 2007-12-18.23:52:12
SpamBayes Score 0.17369924
Marked as misclassified No
Message-id <18280.21621.127241.383744@montanaro.dyndns.org>
In-reply-to <1198004599.56.0.506061970221.issue1580@psf.upfronthosting.co.za>
Content
Guido> ... trying to explain why two numbers both print the same but
    Guido> compare unequal ...

This is not a Python-specific issue.  The notion of limited precision was
pounded into our heads in the numerical analysis class I took in college,
1980-ish.  I'm pretty sure that was before both Python and IEEE-754.  I'm
pretty sure I programmed for that class in Fortran.

    Guido> ... (and God forbid anyone proposes adding fuzz to float ==).

Is it possible to produce a FuzzyFloat class which is a subclass of float
that people could use where they needed it?  Its constructor could take a
tolerance arg, or it could be initialized from a global default.  I'm not
suggesting that suchh a class replace float in the core, but that it might
be useful to have it available in some contexts (available via PyPI, of
course).  I'm offline at the moment or I'd poke around before asking.

Skip
History
Date User Action Args
2007-12-18 23:52:13skip.montanarosetspambayes_score: 0.173699 -> 0.17369924
recipients: + skip.montanaro, gvanrossum, tim.peters, nascheme, rhettinger, christian.heimes, noam
2007-12-18 23:52:12skip.montanarolinkissue1580 messages
2007-12-18 23:52:12skip.montanarocreate