[Twisted-Python] Solved? Or Not? testing my application

Jp Calderone exarkun at divmod.com
Fri Oct 21 23:43:58 EDT 2005

On Thu, 20 Oct 2005 18:07:19 +0200, Marcin Kasperski <marcin.kasperski at softax.com.pl> wrote:
>> As one more attempt I just ugraded from twisted 1.3 to twisted
>> 2.0 (= from twisted version present in Debian testing to
>> twisted version present in Debian unstable).
>> And now ........ the script which in 1.3 ignored errors but
>> worked, *hangs(, in exactly the same way in which it used to
>> hang when I used deferredResult.
>I found the solution. The following modification caused
>everything to work as expected
>    def setUp(self):
>        self.dbpool = adbapi.ConnectionPool('psycopg', DSN)
>        self.dbpool.start()
>        # ...
>(I added self.dbpool.start())
>Confusing part is that start method doc tells:
>            If you are using the reactor normally, this function
>            does *not* need to be called.
>So it seems trial is *not* using reactor 'normally' - whatever
>does it mean.

Indeed.  Hopefully this will be rectified at some future point, but it is difficult to fix for now, due to the way the vast majority of existing tests
are written, along with the desire to retain backwards compatibility.


More information about the Twisted-Python mailing list