This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gregory.p.smith
Recipients astrand, brian.curtin, ezio.melotti, giampaolo.rodola, gregory.p.smith, martin.panter, milko.krachounov, python-dev, tshepang
Date 2015-11-16.02:35:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447641311.1.0.389987470901.issue6973@psf.upfronthosting.co.za>
In-reply-to
Content
I chose to go with the "there should not be an error" approach similar to how Python deals with multiple file closes.  Both are technically programming errors but the point of Python is make life easier.

Reasoning?  I don't want someone to ever think they could depend on getting an exception from send_signal/terminate/kill in this "process has already died and someone has called wait or poll to get its return code" situation as that is unreliable and potentially impacts other innocent processes.
History
Date User Action Args
2015-11-16 02:35:11gregory.p.smithsetrecipients: + gregory.p.smith, astrand, giampaolo.rodola, ezio.melotti, brian.curtin, milko.krachounov, tshepang, python-dev, martin.panter
2015-11-16 02:35:11gregory.p.smithsetmessageid: <1447641311.1.0.389987470901.issue6973@psf.upfronthosting.co.za>
2015-11-16 02:35:11gregory.p.smithlinkissue6973 messages
2015-11-16 02:35:10gregory.p.smithcreate