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 georg.brandl, mark.dickinson
Date 2008-07-26.14:14:55
SpamBayes Score 8.1974e-06
Marked as misclassified No
Message-id <>
Thanks.  Those are the results I'd expect on x86.  So here's the puzzle:

On lines 658-9 of Lib/test/, in revision 65248 of the py3k 
branch, there's a pair of lines that looks like:

        if 1e16+2.999 != 1e16+2.9999:

These lines are supposed to bail out of testSum on IEEE 754 hardware 
that doesn't do correct rounding.  So on your machine, I'd expect:

1e16+2.999  to evaluate to 10000000000000002.0
1e16+2.9999 to evaluate to 10000000000000004.0

so the condition in the if statement ought to be True, and the rest of 
the tests should be skipped.

It looks like this bailout is working as intended in the trunk, but not 
in Py3k.  Any ideas why there's a difference?  Is there some sort of 
constant folding going on in py3k but not in the trunk?
Date User Action Args
2008-07-26 14:14:57mark.dickinsonsetspambayes_score: 8.1974e-06 -> 8.1974e-06
recipients: + mark.dickinson, georg.brandl
2008-07-26 14:14:57mark.dickinsonsetspambayes_score: 8.1974e-06 -> 8.1974e-06
messageid: <>
2008-07-26 14:14:56mark.dickinsonlinkissue3421 messages
2008-07-26 14:14:55mark.dickinsoncreate