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 larry, lemburg, mark.dickinson, rhettinger, serhiy.storchaka, stutzbach, vstinner, vxgmichel
Date 2020-02-03.17:51:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580752283.97.0.331263318845.issue39484@roundup.psfhosted.org>
In-reply-to
Content
> int/int is less accurate than float/float for t=1580301619906185300

No, int/int is more accurate here. If a and b are ints, a / b is always correctly rounded on an IEEE 754 system, while float(a) / float(b) will not necessarily give a correctly rounded result. So for an integer a, `a / 10**9` will _always_ be at least as accurate as `a / 1e9`.
History
Date User Action Args
2020-02-03 17:51:24mark.dickinsonsetrecipients: + mark.dickinson, lemburg, rhettinger, vstinner, larry, stutzbach, serhiy.storchaka, vxgmichel
2020-02-03 17:51:23mark.dickinsonsetmessageid: <1580752283.97.0.331263318845.issue39484@roundup.psfhosted.org>
2020-02-03 17:51:23mark.dickinsonlinkissue39484 messages
2020-02-03 17:51:23mark.dickinsoncreate