On Fri, Feb 29, 2008 at 11:55 AM, Fred Drake <[EMAIL PROTECTED]> wrote:
> They were failing for me a couple of days ago; checking now, they
> still are, and test_itertools has been added to the list of failing
> tests:
>
> test test_itertools failed -- Traceback (most recent call last):
> File "/Users/fdrake/projects/python/py3k/Lib/test/
> test_itertools.py", line 698, in test_chain
> self.assertRaises(TypeError, chain, N(s))
> AssertionError: TypeError not raised by chain
>
This looks like an easy one: line 698 of test_itertools.py should
be changed from
self.assertRaises(TypeError, chain, N(s))
to
self.assertRaises(TypeError, list, chain(N(s)))
Here N(s) is an instance of a class lacking a __next__
method; It looks like Raymond recently altered itertools.chain
to consume its arguments lazily, so the TypeError used to occur
as soon as chain(N(s)) was called, and now doesn't happen
until chain(N(s)).__next__ is first callled.
Shall I check in this fix?
Mark
_______________________________________________
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
