From 26a96fa493361ca098e3df3ab0e04c75e694b6ab Mon Sep 17 00:00:00 2001 From: Mark Dickinson Date: Sat, 1 Mar 2008 02:27:46 +0000 Subject: [PATCH] Fix failing itertools test: since revision 61118, itertools.chain consumes its arguments lazily, so chain(non_iterable) doesn't raise TypeError until the first call to__next__. The test has been changed to reflect this. Committing this in during the code freeze; the checkin was approved by Barry. --- Lib/test/test_itertools.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Lib/test/test_itertools.py b/Lib/test/test_itertools.py index b1c1033f422..44762eb49dd 100644 --- a/Lib/test/test_itertools.py +++ b/Lib/test/test_itertools.py @@ -695,7 +695,7 @@ class TestVariousIteratorArgs(unittest.TestCase): self.assertEqual(list(chain(g(s))), list(g(s))) self.assertEqual(list(chain(g(s), g(s))), list(g(s))+list(g(s))) self.assertRaises(TypeError, list, chain(X(s))) - self.assertRaises(TypeError, chain, N(s)) + self.assertRaises(TypeError, list, chain(N(s))) self.assertRaises(ZeroDivisionError, list, chain(E(s))) def test_product(self):