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? Cheers, -kyle _______________________________________________ Twisted mailing list -- twisted@python.org To unsubscribe send an email to twisted-le...@python.org https://mail.python.org/mailman3/lists/twisted.python.org/ Message archived at https://mail.python.org/archives/list/twisted@python.org/message/7KFG4O2VBV4ZSPOK4Z5RQ5PZGZDTZNEU/ Code of Conduct: https://twisted.org/conduct
