original ) (raw ) Issue12091
Created on 2011-05-16 19:52 by neologix , last changed 2022-04-11 14:57 by admin . This issue is now closed .
Files
File name
Uploaded
Description
Edit
multiprocessing_event.diff neologix,2011-05-16 19:52
patch replacing custom signaling scheme with threading.Event
review
Messages (2)
msg136122 - (view) Author: Charles-François Natali (neologix) *
Date: 2011-05-16 19:52
Multiprocessing's MapResult and ApplyResult use a notification mechanism to signal callers when the underlying value is available. Instead of re-inventing the wheel, we could use threading.Event instead: this leads to cleaner and simpler code (with no noticable performance impact). Patch attached.
msg161579 - (view) Author: Roundup Robot (python-dev)
Date: 2012-05-25 12:29
New changeset 57d6265beaaa by Richard Oudkerk in branch 'default': Issue #12091 : simplify ApplyResult and MapResult with threading.Event http://hg.python.org/cpython/rev/57d6265beaaa
History
Date
User
Action
Args
2022-04-11 14:57:17
admin
set
github: 56300
2012-05-25 19:40:08
sbt
set
status: open -> closedresolution: fixedstage: patch review -> resolved
2012-05-25 12:29:01
python-dev
set
nosy: + python-dev messages: +
2012-05-16 16:44:38
pitrou
set
nosy: + sbt
2011-05-17 14:08:43
pitrou
set
nosy: + pitrou
2011-05-16 19:52:30
neologix
create
