Tue, 3 Jan 2012 17:24:44 +0100 Jérôme a écrit: > > Too many libraries do too many questionable things with signal handlers > > so I find it much safer and easier just to avoid the damn things whenever > > possible. > > My small program _seems to_ work with the dirty hacks I already exposed. > Yet, I'd rather stay on the safe and easy side, especially in a future > bigger program. Therefore, I'm still interested in a better way to proceed. > > Is there another way to tell beep (or sox) to stop before the end of the > beep ? > > AFAIK, the only way to stop it on console is to feed it Ctrl+C. Should I use > communicate() for that ? How ? Apparently, the following does not work : > > process.communicate("\C-c") >
I've been reading more and what I wrote now appears to me as silly, as Ctrl+C, as I understand, is just a way to send SIGINT... I guess I'll have to do with the signal handling, then. But I think I'm beggining to understand what you (Adam Skutt) meant. This is just as dirty as using Ctrl+C to stop beep when using the console, as opposed to using a software that would wait for a specific keypress to stop (in which case I could use communicate()). -- Jérôme -- http://mail.python.org/mailman/listinfo/python-list