[New-bugs-announce] [issue17018] Inconsistent behaviour of methods waiting for child process
report at bugs.python.org
Wed Jan 23 16:15:21 CET 2013
New submission from Marcin Szewczyk:
I've done some experiments with:
These three methods behave completely different when interrupted with a signal which I find disturbing.
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?
Now I know I can loop around Process.join() and check exitcode or is_alive, but it requires more code.
It has been pointed out that it changed between 2.6 and 2.7.
Associated bug: http://bugs.python.org/issue1731717
I think the behaviour of those three should be at least documented, especially if every one of them behaves differently and it changes between versions.
My environment is:
$ python --version
$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.0 (wheezy)
$ uname -a
Linux magazyn-ziarno 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux
Filing a bug as advised on python-dev mailing list (<kdmikh$h3h$1 at ger.gmane.org>).
title: Inconsistent behaviour of methods waiting for child process
versions: Python 2.7
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce