[issue12091] multiprocessing: simplify ApplyResult and MapResult with threading.Event

2012-05-25 Thread Richard Oudkerk
Changes by Richard Oudkerk : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___

[issue12091] multiprocessing: simplify ApplyResult and MapResult with threading.Event

2012-05-25 Thread Roundup Robot
Roundup Robot added the comment: 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 -- nosy: +python-dev ___ Python tr

[issue12091] multiprocessing: simplify ApplyResult and MapResult with threading.Event

2012-05-16 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue12091] multiprocessing: simplify ApplyResult and MapResult with threading.Event

2011-05-17 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +pitrou ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python

[issue12091] multiprocessing: simplify ApplyResult and MapResult with threading.Event

2011-05-16 Thread Charles-François Natali
New submission from Charles-François Natali : 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