On Sun, 20 Feb 2022 at 22:48, Kyle Altendorf <[email protected]> wrote: > > On Sun, Feb 20, 2022, at 13:44, Chris Withers wrote: > > At this point, it feels like any available energy could be more usefully > > employed in getting a pytest plugin that really supported the Twisted > > reactor in place. Re-inventing wheels like coverage just doesn't seem > > sensible at this point. > > I don't expect to invest a lot of time in pytes-twisted, but I am curious > what you mean by supporting the Twisted reactor in place. A new reactor for > each test?
FYIW I'm also +1 to try to get Twisted support for pytest , stdlib unit test or nose. I guess that many of the existing Twisted based projects are using `trial` so things are not that easy. For now, for my project I am running Twisted tests with trial and some custom realtor start and stop, but the long term plan is to migrate to pytest. Regards -- Adi Roiban _______________________________________________ Twisted mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/UVAEY7T5KAHQOLPWMU2R7MNQVJLKELQY/ Code of Conduct: https://twisted.org/conduct
