[Twisted-Python] t.trial.remote -- does anyone use it?
jonathan.lange at gmail.com
Thu Aug 25 02:05:00 EDT 2005
On 25/08/05, Jp Calderone <exarkun at divmod.com> wrote:
> On Wed, 24 Aug 2005 16:35:18 +1000, Jonathan Lange <jonathan.lange at gmail.com> wrote:
> >Trial currently does some black magic to support remote reporters,
> >defined in t.trial.remote. What use cases does t.trial.remote
> >implement? Does anyone actually use it?
> The reporter API should support Deferreds, but twisted.trial.remote doesn't do anything. I don't see any reason not to delete it (it should have been deleted when all its functionality was removed).
No worries. Still, can you please provide a use case?
> >Let me know if you use it. If you don't, I'll remove the code (in my
> >branch) at my next hacking session :)
> Be careful about letting that branch get too big or too old. The smaller it is, the easier it will be to review and merge into trunk. The younger it is, the less the chance it will conflict with other changes.
Good call. I think its ready to go in as it stands. Please review
As far as I can tell, the only API change is that setUpReporter and
tearDownReporter are now assumed to be synchronous.
More information about the Twisted-Python