[issue31863] Inconsistent returncode/exitcode for terminated child processes on Windows

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

I would like to know what our resident Windows users think about this (Paul, Steve, Zach).

Reading the above arguments, I'd be inclined to settle on 15 (that is, the non-negative "signal" number).  While it is not consistent with what "taskkill" or other APIs do, it makes it clear that the process was terminated in a certain way.  Certainly, there is a slight chance that 15 is a legitimate error code returned by the process, but that is far less likely than returning 1 as a legitimate error code, which I presume is extremely common.

In any case, this can't go in a bugfix release, so marking as 3.7-only.

----------
versions:  -Python 3.6, Python 3.8

_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue31863>
_______________________________________