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 belopolsky, drj, ggenellina, mark.dickinson, vstinner
Date 2009-04-02.17:15:54
SpamBayes Score 4.09824e-11
Marked as misclassified No
Message-id <>
Updated patch;  applies cleanly to current trunk.  No significant changes.

Note that there's now a new reason to apply this patch: it ensures that 
the result of a long->float conversion is independent of whether we're 
using 30-bit digits or 15-bit digits for longs.

One problem:  if long->float conversions are correctly rounded, then
int->float conversions should be correctly rounded as well.  (And ideally, 
we should have float(int(n)) == float(long(n)) for any integer n.)

This problem only affects 64-bit machines:  on 32-bit machines, all 
integers are exactly representable as floats, and the C99 standard 
specifies that in that case the conversion should be exact.
Date User Action Args
2009-04-02 17:16:05mark.dickinsonsetrecipients: + mark.dickinson, belopolsky, ggenellina, vstinner, drj
2009-04-02 17:16:03mark.dickinsonsetmessageid: <>
2009-04-02 17:16:02mark.dickinsonlinkissue3166 messages
2009-04-02 17:16:01mark.dickinsoncreate