Issue 10673: multiprocess.Process join method - timeout indistinguishable from success (original ) (raw )Created on 2010-12-10 14:36 by Brian.Cain , last changed 2022-04-11 14:57 by admin . This issue is now closed .
Messages (9)
msg123733 - (view)
Author: Brian Cain (Brian.Cain) *
Date: 2010-12-10 14:36
When calling Process' join([timeout]) method, the timeout expiration case is indistinguishable from the successful join. I suppose the 'exitcode' attribute can deliver the necessary information, but perhaps join could stand on its own. If join() shouldn't be changed, could we make explicit reference to the exitcode attribute in the documentation?
msg123735 - (view)
Author: R. David Murray (r.david.murray) *
Date: 2010-12-10 15:26
My guess is "it shouldn't", and "yes", but I've added the multiprocessing maintainers as nosy and they can answer definitively.
msg123736 - (view)
Author: Ask Solem (asksol)
Date: 2010-12-10 15:36
While it makes sense for `join` to raise an error on timeout, that could possibly break existing code, so I don't think that is an option. Adding a note in the documentation would be great.
msg271724 - (view)
Author: Berker Peksag (berker.peksag) *
Date: 2016-07-31 06:32
Thread.join() also returns None in all cases so +1 for documenting the current behavior.
msg275944 - (view)
Author: Tom Clark (tclark) *
Date: 2016-09-12 04:14
I've submitted a documentation patch with #28094 .
msg275954 - (view)
Author: Tom Clark (tclark) *
Date: 2016-09-12 04:33
This patch is intended to document the behaviour of join(). (Originally submitted to #28094 )
msg275955 - (view)
Author: Berker Peksag (berker.peksag) *
Date: 2016-09-12 04:37
Tom's patch looks good to me. Davin, can you have a look at it?
msg277461 - (view)
Author: Roundup Robot (python-dev)
Date: 2016-09-26 20:21
New changeset 112060f8abe8 by Berker Peksag in branch '3.5': Issue #10673 : Document that Process.exitcode can be used to determine timeout https://hg.python.org/cpython/rev/112060f8abe8 New changeset 0414ce8a3b5c by Berker Peksag in branch '3.6': Issue #10673 : Merge from 3.5 https://hg.python.org/cpython/rev/0414ce8a3b5c New changeset f91650739061 by Berker Peksag in branch 'default': Issue #10673 : Merge from 3.6 https://hg.python.org/cpython/rev/f91650739061
msg277462 - (view)
Author: Berker Peksag (berker.peksag) *
Date: 2016-09-26 20:21
Thanks, Tom.
History
Date
User
Action
Args
2022-04-11 14:57:10
admin
set
github: 54882
2016-09-26 20:21:45
berker.peksag
set
status: open -> closedversions: + Python 3.7messages: + components: - Library (Lib)resolution: fixedstage: patch review -> resolved
2016-09-26 20:21:16
python-dev
set
nosy: + python-dev messages: +
2016-09-13 20:35:23
ppperry
set
assignee: docs@python components: + Documentationnosy: + docs@python
2016-09-12 04:37:32
berker.peksag
set
messages: + stage: needs patch -> patch review
2016-09-12 04:34:00
tclark
set
files: + multiprocessing.patch messages: +
2016-09-12 04:29:56
berker.peksag
link
issue28094 superseder
2016-09-12 04:14:07
tclark
set
nosy: + tclark messages: +
2016-08-01 02:23:09
ned.deily
set
nosy: + davin
2016-07-31 06:32:37
berker.peksag
set
versions: + Python 3.5, Python 3.6, - Python 3.3nosy: + berker.peksag messages: + keywords: + easy stage: needs patch
2011-01-03 19:57:11
pitrou
set
nosy:jnoller , r.david.murray , asksol , Brian.Cain versions: + Python 3.3, - Python 3.1, Python 2.7
2010-12-10 15:36:31
asksol
set
messages: +
2010-12-10 15:26:18
r.david.murray
set
nosy: + asksol , r.david.murray , jnoller messages: +
2010-12-10 14:36:02
Brian.Cain
create