[Twisted-Python] t.trial.remote -- does anyone use it?
Hello, 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? Rumour has it that it was originally written to make buildbot easier to write. However, I'm told that buildbot just parses stdio output. Let me know if you use it. If you don't, I'll remove the code (in my branch) at my next hacking session :) cheers, jml
Hi, I'd like to try out twisted.news, but the documentation seems to be missing at the moment. Also on running setup.py I get the warning package init file 'twisted/plugins/__init__.py' not found (or not a regular file) Can I just ignore it? Many thanks for the support, Graham
On Wed, 24 Aug 2005 16:35:18 +1000, Jonathan Lange <jonathan.lange@gmail.com> wrote:
Hello,
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?
Rumour has it that it was originally written to make buildbot easier to write. However, I'm told that buildbot just parses stdio output.
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).
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. Jp
On 25/08/05, Jp Calderone <exarkun@divmod.com> wrote:
On Wed, 24 Aug 2005 16:35:18 +1000, Jonathan Lange <jonathan.lange@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 it (anyone). As far as I can tell, the only API change is that setUpReporter and tearDownReporter are now assumed to be synchronous. thanks, jml
participants (3)
-
Graham Stratton -
Jonathan Lange -
Jp Calderone