Richard Oudkerk shibt...@gmail.com added the comment:
The patch was applied to 3.x branch in 0aa8af79359d and partially backported to
2.7 in 26bbff4562a7 - see #9400.
I will close.
--
nosy: +sbt
resolution: - fixed
stage: - committed/rejected
status: open - closed
Roundup Robot devn...@psf.upfronthosting.co.za added the comment:
New changeset 26bbff4562a7 by Richard Oudkerk in branch '2.7':
Issue #9400: Partial backport of fix for #9244
http://hg.python.org/cpython/rev/26bbff4562a7
--
nosy: +python-dev
___
Jesse Noller jnol...@gmail.com added the comment:
Fine w/ committing this Ask.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9244
___
___
Ask Solem a...@opera.com added the comment:
Updated patch with Greg's suggestions.
(multiprocessing-tr...@82502-handle_worker_encoding_errors2.patch)
--
Added file:
http://bugs.python.org/file18014/multiprocessing-tr...@82502-handle_worker_encoding_errors2.patch
Ask Solem a...@opera.com added the comment:
To be clear, the errback change and the unpickleable result
change are actually orthogonal, right?
Yes, it could be a separate issue. Jesse, do you think I should I open
up a separate issue for this?
Why not add an error_callback for map_async as
Changes by Ask Solem a...@opera.com:
--
title: multiprocessing.pool: Pool crashes if worker can't encode result (with
patch) - multiprocessing.pool: Worker crashes if result can't be encoded
result (with patch)
___
Python tracker
Changes by Ask Solem a...@opera.com:
--
title: multiprocessing.pool: Worker crashes if result can't be encoded result
(with patch) - multiprocessing.pool: Worker crashes if result can't be encoded
___
Python tracker rep...@bugs.python.org
Changes by Jesse Noller jnol...@gmail.com:
--
assignee: - jnoller
nosy: +gdb
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9244
___
___
Greg Brockman g...@ksplice.com added the comment:
This looks pretty reasonable to my untrained eye. I successfully applied and
ran the test suite.
To be clear, the errback change and the unpickleable result change are actually
orthogonal, right? Anyway, I'm not really familiar with the
