Message305598
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. |
|
Date |
User |
Action |
Args |
2017-11-05 15:08:20 | pitrou | set | recipients:
+ pitrou, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, davin, Akos Kiss |
2017-11-05 15:08:20 | pitrou | set | messageid: <1509894500.66.0.213398074469.issue31863@psf.upfronthosting.co.za> |
2017-11-05 15:08:20 | pitrou | link | issue31863 messages |
2017-11-05 15:08:20 | pitrou | create | |
|