On Sat, 11 Apr 2009 00:24:37 +0200, luper rouch luper.ro...@gmail.com wrote:
I would like to port my Application API based services to the twistd
plugin interface, to be able to retrieve command line options.
In the existing services, I reimplemented t.a.s.MultiService
startService() and
2009/4/11 Jean-Paul Calderone exar...@divmod.com:
On Sat, 11 Apr 2009 00:24:37 +0200, luper rouch luper.ro...@gmail.com
wrote:
I would like to port my Application API based services to the twistd
plugin interface, to be able to retrieve command line options.
In the existing services, I
Hi Luper
luper == luper rouch luper.ro...@gmail.com writes:
luper I have a last question, I put my plugins in a 'twisted/plugins'
luper subfolder of my project, and running them from the command line
luper works fine. How can I invoke them in unit tests (I need to be able
luper to start and
2009/4/11 Esteve Fernandez est...@sindominio.net:
On Saturday 11 April 2009 19:42:31 Jean-Paul Calderone wrote:
They can be imported from twisted.plugins. For example, if you name your
dropin file foo_plugins.py, then from twisted.plugins import
foo_plugins should work and let you test any
On 11 Apr, 08:39 pm, exar...@divmod.com wrote:
On Sat, 11 Apr 2009 21:54:08 +0200, Esteve Fernandez
est...@sindominio.net wrote:
Shouldn't twisted and twisted/plugins be non-importable? I thought
twisted and
twisted/plugins must not have __init__.py files in order for the
plugin
system to
