[Twisted-Python] Re: Using twisted.trial with nose unittest system

[Allen Bierbaum]

Is there anything that could be ported over from trial and used in the
nose plugin to make things behave better.  All I am really interested
in is allowing twisted code to be tested in the best way possible from
within nose.  The current plugin seems to work well, but if there are
ways to make it work better I am all for using them.

For example earlier in the thread Johnathan mentioned that it may be
possible to just derive from twisted.trial.unittest.TestCase directly.

Antoine: Did you try this when making the nose plugin and what
problems did you run into?


-Allen


On 2/7/07, Jean-Paul Calderone <exarkun at divmod.com> wrote:
> On Wed, 07 Feb 2007 16:32:26 +0100, Antoine Pitrou <antoine.pitrou at wengo.com> wrote:
> >
> >Hi Jean-Paul,
> >
> >> The one practical problem which this method of integration has is that
> >> it will not allow unit tests to run child processes.  So, one wouldn't
> >> be able to run Twisted's test suite with nose using this.  Of course,
> >> if one has no interest in running tests which run child processes, then
> >> this may not be a big deal.
> >
> >Do you mean because the reactor does not receive signals?
> >
>
> Yep.  Without the SIGCHLD handler installed, Twisted will never reap the
> children, so they will remain as zombies.
>
> Jean-Paul
>
> _______________________________________________
> Twisted-Python mailing list
> Twisted-Python at twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
>