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 mark.dickinson, serhiy.storchaka, zach.ware
Date 2020-05-28.18:26:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> Converting Decimal, Fraction, float128 to float before using it in expression can lead to loss of precision.

My experience is that this loss of precision is hardly ever a practical problem in the real world of scientific development; in practice floating-point numbers  are almost universally IEEE 754 doubles (perhaps sometimes single-precision in large datasets, like seismic SEG-Y files; occasionally IBM format hex floats; but IEEE 754 doubles are by far the majority). It's very rare to be using float128 or Decimal or Fraction in practice for scientific data.

That's not to say that people outside that world won't be using these things, but there's a big ecosystem where float64 is pretty much all you need.
Date User Action Args
2020-05-28 18:26:20mark.dickinsonsetrecipients: + mark.dickinson, zach.ware, serhiy.storchaka
2020-05-28 18:26:20mark.dickinsonsetmessageid: <>
2020-05-28 18:26:20mark.dickinsonlinkissue40801 messages
2020-05-28 18:26:19mark.dickinsoncreate