<br><br><div><span class="gmail_quote">On 4/6/07, <b class="gmail_sendername">holger krekel</b> <<a href="mailto:holger@merlinux.de">holger@merlinux.de</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Ralf,<br><br>sorry for missing out on answering.</blockquote><div><br>no problem. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tue, Feb 20, 2007 at 10:20 +0100, Ralf Schmitt wrote:<br>> Hi all,<br>><br>> I've made py.test work with the twisted framework using greenlets to switch<br>> between twisted's mainloop and py.test's "mainloop". (see attached file).
<br>> It currently uses monkeypatching to change py.test.Item's execute function.<br>> Currently missing is the ability to return twisted deferreds from setup and<br>> teardown methods.<br>> I could monkeypatch
py.test even more, but I'd rather have a method to hook<br>> into py.test, and intercept any calls to user supplied functions (i.e.<br>> teardown, setup, and test methods). Any chance to get such changes<br>> integrated into
py.test? I'd be willing to write them on my own and would<br>> also be glad to have the py.test.twisted script be included into py.test.<br><br>yes, let's consider how to integrate twisted support - however,<br>
from my side not much before May - i still need to recover<br>from the recent PyPy release and report rushs ...</blockquote><div><br>Hope you recovered. Do you have time to discuss twisted support now?<br><br>Regards,<br>
- Ralf<br><br></div></div>