Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #36996 > unrolled thread
| Started by | Marcin Szewczyk <python-list@wodny.org> |
|---|---|
| First post | 2013-01-18 13:04 +0100 |
| Last post | 2013-01-18 13:04 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
Inconsistent behaviour of methods waiting for child process Marcin Szewczyk <python-list@wodny.org> - 2013-01-18 13:04 +0100
| From | Marcin Szewczyk <python-list@wodny.org> |
|---|---|
| Date | 2013-01-18 13:04 +0100 |
| Subject | Inconsistent behaviour of methods waiting for child process |
| Message-ID | <mailman.627.1358514450.2939.python-list@python.org> |
Hi, I've done some experiments with: 1) multiprocessing.Process.join() 2) os.waitpid() 3) subprocess.Popen.wait() These three methods behave completely different when interrupted with a signal which I find disturbing. Reactions are: 1) exit with no exception or special return code 2) OSError exception 3) quiet retry (no exit) The 1) case is very impractical. Is there any movement towards standardization of those 3? Am I missing something and there is a way to get more information from Process.join()? -- Marcin Szewczyk http://wodny.org mailto:Marcin.Szewczyk@wodny.borg <- remove b / usuĊ b xmpp:wodny@ubuntu.pl xmpp:wodny@jabster.pl
Back to top | Article view | comp.lang.python
csiph-web