Reverting the patch that tried to fix the issue whereby x**2 raises

OverflowError while x*x succeeds and produces infinity; apparently
these inconsistencies cannot be fixed across ``all'' platforms and
there's a widespread feeling that therefore ``every'' platform
should keep suffering forevermore.  Ah well.

1 files changed, 1 insertions, 14 deletions

diff --git a/Lib/test/test_float.py b/Lib/test/test_float.py
index d616ad9..fb47db8 100644
--- a/Lib/test/test_float.py
+++ b/Lib/test/test_float.py
@@ -99,25 +99,12 @@ class IEEEFormatTestCase(unittest.TestCase):
                               ('<f', LE_FLOAT_NAN)]:
                 struct.unpack(fmt, data)
 
-# on an IEEE platform, "overflowing" operations produce infinity
-
-class IEEEOperationsTestCase(unittest.TestCase):
-    if float.__getformat__("double").startswith("IEEE"):
-        def test_double_infinity(self):
-            big = 4.8e159
-            pro = big*big
-            self.assertEquals(repr(pro), 'inf')
-            sqr = big**2
-            self.assertEquals(repr(sqr), 'inf')
-
 
 def test_main():
     test_support.run_unittest(
         FormatFunctionsTestCase,
         UnknownFormatTestCase,
-        IEEEFormatTestCase,
-        IEEEOperationsTestCase,
-        )
+        IEEEFormatTestCase)
 
 if __name__ == '__main__':
     test_main()