diff options
| author | Tim Peters <tim.peters@gmail.com> | 2001-09-06 23:00:21 (GMT) |
|---|---|---|
| committer | Tim Peters <tim.peters@gmail.com> | 2001-09-06 23:00:21 (GMT) |
| commit | c5b235c59c956ec972521ac0b0e5dc3aa56ca19a (patch) | |
| tree | 646d364591c3ef6e00f1d795571ebd7da96320f1 /Lib/test/test_long_future.py | |
| parent | 419670dc6017b5b463c88b08b4855aa7c9d396a3 (diff) | |
| download | cpython-c5b235c59c956ec972521ac0b0e5dc3aa56ca19a.zip cpython-c5b235c59c956ec972521ac0b0e5dc3aa56ca19a.tar.gz cpython-c5b235c59c956ec972521ac0b0e5dc3aa56ca19a.tar.bz2 | |
Reverting to rev 1.2. Apparently gcc doesn't use the extended-precision
capabilities of the Pentium FPU, so what should have been (and were on
Windows) exact results got fuzzy. Then it turns out test_support.fcmp()
isn't tolerant of tiny errors when *one* of the comparands is 0, but
test_complex's old check_close_real() is. Rather than fix gcc <wink>,
easier to revert this test and revisit after the release.
Diffstat (limited to 'Lib/test/test_long_future.py')
0 files changed, 0 insertions, 0 deletions