A
Ami Tavory
From: Peter Otten <[email protected]>
To: (e-mail address removed)
Cc:
Date: Thu, 14 Feb 2013 09:00:58 +0100
.... yield 42
.... finally:
.... 1/0
........ break
....
Exception ZeroDivisionError: 'integer division or modulo by zero' in
<generator object g at 0x7f990243b0f0> ignored
Can you exhaust the generator?
.... pass
....
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 5, in g
ZeroDivisionError: integer division or modulo by zero
Explicitly closing the generator seems to work, too:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 5, in g
ZeroDivisionError: integer division or modulo by zero
-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
Hi Peter,
Thanks for your answer!
So basically the thing is that, as you've shown, if you exhaust a
generator or force-close it, an exception is indeed thrown. However, in
this were the case then unittest would identify it as a problem, and I
could relatively easily get a traceback and see from where it's
originating. However, the unittests are passing fine (except for the pesky
messages), so it's something else.
I'm starting to think that what's happening is something like this: I
have a cascade of generator objects (some hold on to others), and the
unittests check both the exhaustion case and the non-exhaustion case (both
cases are valid use cases). *Later on*, after the tests finish, the garbage
collector starts tearing down the generator cascade, but in a different
order. Some generators, while closing down, are attempting to close down
other generators that no longer exist.
So, notwithstanding your correct answer - I'm still stumped about finding
out how to get rid of these annoying messages.
Thanks,
Ami
To: (e-mail address removed)
Cc:
Date: Thu, 14 Feb 2013 09:00:58 +0100
.... try:
.... yield 42
.... finally:
.... 1/0
........ break
....
Exception ZeroDivisionError: 'integer division or modulo by zero' in
<generator object g at 0x7f990243b0f0> ignored
Can you exhaust the generator?
.... pass
....
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 5, in g
ZeroDivisionError: integer division or modulo by zero
Explicitly closing the generator seems to work, too:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "<stdin>", line 5, in g
ZeroDivisionError: integer division or modulo by zero
-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------
Hi Peter,
Thanks for your answer!
So basically the thing is that, as you've shown, if you exhaust a
generator or force-close it, an exception is indeed thrown. However, in
this were the case then unittest would identify it as a problem, and I
could relatively easily get a traceback and see from where it's
originating. However, the unittests are passing fine (except for the pesky
messages), so it's something else.
I'm starting to think that what's happening is something like this: I
have a cascade of generator objects (some hold on to others), and the
unittests check both the exhaustion case and the non-exhaustion case (both
cases are valid use cases). *Later on*, after the tests finish, the garbage
collector starts tearing down the generator cascade, but in a different
order. Some generators, while closing down, are attempting to close down
other generators that no longer exist.
So, notwithstanding your correct answer - I'm still stumped about finding
out how to get rid of these annoying messages.
Thanks,
Ami