➜

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 tim.peters
Recipients mark.dickinson, rhettinger, steven.daprano, tim.peters
Date 2021-11-27.03:16:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1637982974.71.0.682741202626.issue45876@roundup.psfhosted.org>
In-reply-to
Content 
But I would like to leave it alone. Extended precision simply is not an issue on any current platform I'm aware of ("not even Windows"), and I would, e.g., hate trying to explain to users why

    1 / 2731 != 1.0 / 2731.0

(assuming we're not also proposing to take float division away from the HW). It's A Feature that

    I / J == float(I) / float(J)

whenever I and J are both representable as floats.

If extended precision is an issue on some platform, fine, let them speak up. On x87 we could document that CPython assumes the FPU's "precision control" is set to 53 bits.
History
Date User Action Args
2021-11-27 03:16:14tim.peterssetrecipients: + tim.peters, rhettinger, mark.dickinson, steven.daprano
2021-11-27 03:16:14tim.peterssetmessageid: <1637982974.71.0.682741202626.issue45876@roundup.psfhosted.org>
2021-11-27 03:16:14tim.peterslinkissue45876 messages
2021-11-27 03:16:14tim.peterscreate