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 corona10, mark.dickinson, rhettinger, tim.peters
Date 2020-09-22.17:20:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1600795206.29.0.98537469247.issue41823@roundup.psfhosted.org>
In-reply-to
Content
Double rounding is a property of how operations on floats are carried out, rather than being a property of the float format itself; I'm not sure that it belongs in float_info. It's also potentially ill-defined. Right now, as far as I *know*, it seems to be the case that our builds of CPython on x86 or x64 either consistently use x87+extended precision for all floating-point operations, or they consistently use SSE2 for all floating-point operations, but there's no reason that a build couldn't use SSE2 in some cases and x87+extended precision in others. (There are also subtle differences between x87+53-bit precision setting and IEEE 754-following SSE2.)

We also don't have any _reliable_ way to tell whether floats use IEEE 754, though we do have some ad-hoc ways that seem to work in practice (at least for now).
History
Date User Action Args
2020-09-22 17:20:06mark.dickinsonsetrecipients: + mark.dickinson, tim.peters, rhettinger, corona10
2020-09-22 17:20:06mark.dickinsonsetmessageid: <1600795206.29.0.98537469247.issue41823@roundup.psfhosted.org>
2020-09-22 17:20:06mark.dickinsonlinkissue41823 messages
2020-09-22 17:20:06mark.dickinsoncreate