Comment #4 on issue 1515 by pekka.klarck: [Library] Process library add
keyword to send signal to current active process
http://code.google.com/p/robotframework/issues/detail?id=1515
If you want to help, it would be great if you could test how send_signal
works on Windows and possibly elsewhere. The code to implement this is
pretty trivial, I suspect adding something like this to the Process class
ought to be enough:
def send_signal(self, signal):
import signal as signal_module
signal = getattr(signal_module, signal)
process = self._processes[handle]
process.send_signal(signal)
To support those special Windows signals/events, start_process also needs
to be changed so that Popen gets new argument
`creationflags=subprocess.CREATE_NEW_PROCESS_GROUP`.
Things that need to be verified are listed below:
1) Does the above work in general?
2) Do CTRL_C/BREAK_EVENT signals work?
3) Do CTRL_C/BREAK_EVENT signals work when using shell? According to the
subprocess docs, CREATE_NEW_PROCESS_GROUP is ignored if CREATE_NEW_CONSOLE
is specified, and the latter is automatically set when shell=True. Does
that mean that shell=True disables CREATE_NEW_PROCESS_GROUP and thus using
these special signals? We cannot do much to it either way, but the behavior
needs to be documented.
4) Is it OK to use creationflags with non-zero value outside Windows?
5) How does the above work with Jython and IronPython? At least send_signal
will not work with Jython 2.5. Most importantly we need to know does using
creatingflags cause issues.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
