➜

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 martin.panter
Recipients Mike Pomraning, SilentGhost, gregory.p.smith, martin.panter, rpcope1, vstinner
Date 2017-11-06.04:59:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1509944383.4.0.213398074469.issue25942@psf.upfronthosting.co.za>
In-reply-to
Content 
https://github.com/python/cpython/pull/4283 adds a secondary timeout, which defaults to 1 s when there is no main timeout. But this seems complicated and arbitrary. As I understand, the main use case discussed here was waiting without a timeout for a child that exits soon after the interrupt. But are there any practical use cases or demand for:

* Limiting the wait time after the interrupt (despite no timeout before the interrupt)?
* Customizing this additional timeout?
History
Date User Action Args
2017-11-06 04:59:43martin.pantersetrecipients: + martin.panter, gregory.p.smith, vstinner, SilentGhost, Mike Pomraning, rpcope1
2017-11-06 04:59:43martin.pantersetmessageid: <1509944383.4.0.213398074469.issue25942@psf.upfronthosting.co.za>
2017-11-06 04:59:43martin.panterlinkissue25942 messages
2017-11-06 04:59:42martin.pantercreate