Fix xrange tests now that xrange() (like many other places) no longer

silently converts floats to integers when expecting integer values.
This commit is contained in:
Thomas Wouters 2006-04-17 13:16:50 +00:00
parent ba617af298
commit 07519f8712
1 changed files with 4 additions and 1 deletions

View File

@ -43,7 +43,10 @@ class XrangeTest(unittest.TestCase):
self.assertRaises(TypeError, xrange, 1, 2, 3, 4)
self.assertRaises(ValueError, xrange, 1, 2, 0)
self.assertRaises(OverflowError, xrange, 1e100, 1e101, 1e101)
self.assertRaises(TypeError, xrange, 0.0, 2, 1)
self.assertRaises(TypeError, xrange, 1, 2.0, 1)
self.assertRaises(TypeError, xrange, 1, 2, 1.0)
self.assertRaises(TypeError, xrange, 1e100, 1e101, 1e101)
self.assertRaises(TypeError, xrange, 0, "spam")
self.assertRaises(TypeError, xrange, 0, 42, "spam")