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 christian.heimes, gvanrossum, nascheme, noam, tim.peters
Date 2007-12-11.03:15:05
SpamBayes Score 0.051279597
Marked as misclassified No
Message-id <>
Again, without replacing float input routines too, this is /not/ good
enough to ensure eval(repr(x)) == x even across just 100%-conforming 754

It is good enough to ensure (well, assuming the code is 100% correct)
eval(repr(x)) == x across conforming 754 platforms that go /beyond/ the
standard by also supplying correctly rounding input routines.  Some
platform C libraries do, some don't.  For example, I believe glibc does
(and builds its I/O code on David Gay's, mentioned before), but that
Microsoft's does not (but that Microsoft's do meet the 754 standard,
which-- again --isn't strong enough for "shortest output" to round-trip
correctly in all cases).
Date User Action Args
2007-12-11 03:15:06tim.peterssetspambayes_score: 0.0512796 -> 0.051279597
recipients: + tim.peters, gvanrossum, nascheme, christian.heimes, noam
2007-12-11 03:15:06tim.peterssetspambayes_score: 0.0512796 -> 0.0512796
messageid: <>
2007-12-11 03:15:06tim.peterslinkissue1580 messages
2007-12-11 03:15:05tim.peterscreate