Cameron Simpson writes:
[...]
> What if you did this:
>
> os.signal(SIGINT, SIG_IGN)
> ... code code code, including the Popen/wait ...
> old_handler = os.signal(SIGINT, do_nothing_handler)
> sleep(...)
> os.signal(SIGINT, old_handler)
>
> SIG_IGN is different from a do-nothing handler; it
On 28Oct2017 23:56, Piet van Oostrum wrote:
I am using Python 2.7.14 on MacOS Sierra.
I have a small Python program that calls a shell script in a loop with a
time.sleep() in it.
The shell script is called with subprocess.Popen(), followed by a
subprocess.wait().
No information is exchanged w
On 29Oct2017 10:11, Cameron Simpson wrote:
It may be a bug. Or it may be a system call which cannot be meaningfulling
retried. But had you considered only activating the handler around the sleep?
You still need to copy with SIGINT single I infer that you send this from
outside the program.
On Sun, Oct 29, 2017 at 8:56 AM, Piet van Oostrum wrote:
> I am using Python 2.7.14 on MacOS Sierra.
>
> I have a small Python program that calls a shell script in a loop with a
> time.sleep() in it.
> The shell script is called with subprocess.Popen(), followed by a
> subprocess.wait().
> No in
I am using Python 2.7.14 on MacOS Sierra.
I have a small Python program that calls a shell script in a loop with a
time.sleep() in it.
The shell script is called with subprocess.Popen(), followed by a
subprocess.wait().
No information is exchanged with the shell script.
Once in a while I send a
