#3796: A test class was not run in test_float.

Reviewed by Benjamin.
This commit is contained in:
Amaury Forgeot d'Arc 2008-09-06 20:53:51 +00:00
parent cd52023e6f
commit feb8cade4d
2 changed files with 8 additions and 4 deletions

View File

@ -5,6 +5,7 @@ from test import test_support
import math
from math import isinf, isnan, copysign, ldexp
import operator
import random, fractions
INF = float("inf")
NAN = float("nan")
@ -23,7 +24,7 @@ class GeneralFloatCases(unittest.TestCase):
self.assertRaises(ValueError, float, "+-3.14")
self.assertRaises(ValueError, float, "-+3.14")
self.assertRaises(ValueError, float, "--3.14")
if have_unicode:
if test_support.have_unicode:
self.assertEqual(float(unicode(" 3.14 ")), 3.14)
self.assertEqual(float(unicode(" \u0663.\u0661\u0664 ",'raw-unicode-escape')), 3.14)
# Implementation limitation in PyFloat_FromString()
@ -736,6 +737,7 @@ class HexFloatTestCase(unittest.TestCase):
def test_main():
test_support.run_unittest(
GeneralFloatCases,
FormatFunctionsTestCase,
UnknownFormatTestCase,
IEEEFormatTestCase,

View File

@ -114,13 +114,15 @@ Extension Modules
Tests
-----
- Issue 3768: Move test_py3kwarn over to the new API for catch_warnings().
- Issue #3796: Some tests functions were not enabled in test_float.
- Issue #3768: Move test_py3kwarn over to the new API for catch_warnings().
Build
-----
- Issue 3758: Rename the 'check' target to 'patchcheck' so as to not clash with
GNU build target guidelines.
- Issue #3758: Rename the 'check' target to 'patchcheck' so as to not clash
with GNU build target guidelines.
What's New in Python 2.6 beta 3?