been too busy to work on this, but...
1) Ok, I will avoid subprocess and stick with twisted. Thanks!
2) I will absolutely document where things got annoying to share!
On Sep 27, 2013, at 12:35 AM, Matt Haggard wrote:
>
> On Sep 26, 2013 8:18 PM, "Glyph" wrote:
> >
> >
> > On Sep 26, 2013, a
On 09/27/2013 02:51 AM, Jonathan Vanasco wrote:
i was looking at reactor.SpawnProcess -- which I know is more
correct. it just seems to be a bit annoying to use
Are you aware of twisted.internet.utils.getProcessOutputAndValue? For
simple spawn/check cases, that's pretty much always the best
On Sep 26, 2013 8:18 PM, "Glyph" wrote:
>
>
> On Sep 26, 2013, at 6:51 PM, Jonathan Vanasco
wrote:
>
> Could you write up why you feel it's "annoying"? Maybe we can improve
spawnProcess so it works better for you in the future.
I'm also interested in what you feel is annoying. Please write this
On Sep 26, 2013, at 6:51 PM, Jonathan Vanasco wrote:
>
> Quick question about (sub)processes in twisted :
>
> how bad is it to use the subprocess module ? ( in general / in this
> application )
It's pretty bad ;-).
> I have the following setup :
>
> - Twisted Daemon that does
Quick question about (sub)processes in twisted :
how bad is it to use the subprocess module ? ( in general / in this
application )
I have the following setup :
- Twisted Daemon that does 5 things (very well!)
- A new requirement -- to execute 2 scripts on the commandli
