[Twisted-Python] Bug in reactor.iterate()?

[Sam Couter]

Twisted version: 1.2.0

Attached is a minimal test case to demonstrate behaviour I consider a
bug in reactor.iterate() in the default reactor. You'll need to change
the DB name, user and password, and pick a table that exists in your DB.

The callbacks are never called while iterate() runs, but are called if
iterate() is replaced with run(), or if run() is called after iterate().

Am I correct in considering this a bug?

I found this while creating a unit test following the example at the
bottom of
http://www.twistedmatrix.com/documents/current/howto/test-standard.
-- 
Sam "Eddie" Couter  |  mailto:sam at couter.dropbear.id.au
Debian Developer    |  mailto:eddie at debian.org
                    |  jabber:sam at teknohaus.dyndns.org
OpenPGP fingerprint:  A46B 9BB5 3148 7BEA 1F05  5BD5 8530 03AE DE89 C75C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: iterate.py
Type: text/x-python
Size: 446 bytes
Desc: not available
Url : http://twistedmatrix.com/pipermail/twisted-python/attachments/20040426/edea1073/attachment.py 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://twistedmatrix.com/pipermail/twisted-python/attachments/20040426/edea1073/attachment.pgp