On Mon, Oct 10, 2016 at 12:05 AM, dieter wrote:
> Dan Stromberg writes:
>> I have a program http://stromberg.dnsalias.org/~dstromberg/looper/
>> that I use and maintain.
>>
>> It's like GNU parallel or similar - yet another "run n processes, m at
>> a time" implementation. Interestingly, I've on
Dan Stromberg writes:
> I have a program http://stromberg.dnsalias.org/~dstromberg/looper/
> that I use and maintain.
>
> It's like GNU parallel or similar - yet another "run n processes, m at
> a time" implementation. Interestingly, I've only used/tested it on
> Linux, but it's under a Microsoft
Dan Stromberg :
> That bug is: if you control-C the top-level process, all the
> subprocesses are left running.
Sorry, don't have a solution for your particular Python situation.
> I've been thinking about making it catch SIGINT, SIGTERM and SIGHUP,
> and having it SIGKILL its active subprocesses
Dan Stromberg writes:
> That bug is: if you control-C the top-level process, all the
> subprocesses are left running.
Are you setting the daemon flag?
--
https://mail.python.org/mailman/listinfo/python-list
On Mon, Oct 10, 2016 at 10:52 AM, Dan Stromberg wrote:
> That bug is: if you control-C the top-level process, all the
> subprocesses are left running.
>
> I've been thinking about making it catch SIGINT, SIGTERM and SIGHUP,
> and having it SIGKILL its active subprocesses upon receiving one of
> th
I have a program http://stromberg.dnsalias.org/~dstromberg/looper/
that I use and maintain.
It's like GNU parallel or similar - yet another "run n processes, m at
a time" implementation. Interestingly, I've only used/tested it on
Linux, but it's under a Microsoft copyright because Microsoft acqui
