On 4/12/06, <b class="gmail_sendername">Thomas Vander Stichele</b> <<a href="mailto:thomas@apestaart.org">thomas@apestaart.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>> 2. Trial Reactor (<a href="http://twistedmatrix.com/trac/ticket/1334">http://twistedmatrix.com/trac/ticket/1334</a>)<br>> Jp has indicated that this is the best way for Trial to do cleanup<br>> after each test.
<br><br>How does this work if currently a project chooses a specific reactor<br>because that's what the tests need ?<br><br>For example, some of our UI unit tests use the gtk2reactor/glib2reactor<br>because otherwise they can't run. Same for some of our GStreamer-using
<br>tests, which need a glib main loop.<br><br>Maybe whatever trial needs can be implemented as an IReactorIface or a<br>mixin instead ?</blockquote><div><br><br>If some of your tests are reliant on one reactor, and some of them on another, then you can't run them both in the same process even now. You will have to specify the reactor globally, just as always.
<br><br><br>Oh, now I think I know what you mean: "Is the Trial reactor only compatible with the select reactor?"? As I understand it, the idea is to make it a wrapper around whatever other reactor you globally choose.
</div></div><br>-- <br>Christopher Armstrong<br>International Man of Twistery<br><a href="http://radix.twistedmatrix.com/">http://radix.twistedmatrix.com/</a><br><a href="http://twistedmatrix.com/">http://twistedmatrix.com/
</a><br><a href="http://canonical.com/">http://canonical.com/</a><br>