Jesse Noller jnol...@gmail.com added the comment:
Committed in r73708 on trunk
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5331
___
Jesse Noller jnol...@gmail.com added the comment:
Patch attached to issue 5313, please review
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5331
___
Gabriel de Perthuis ony...@users.sourceforge.net added the comment:
Apparently the pool workers die all at once, just after the pool creates
them and before the pool is used.
I added a few lines to multiprocessing/pool.py to get the stack and the
exception backtrace.
except (EOFError,
OG7 ony...@users.sourceforge.net added the comment:
It seems the root cause is at http://bugs.python.org/issue5155 .
A workaround is to use a duplex Pipe in SimpleQueue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5331
Changes by Jesse Noller jnol...@gmail.com:
--
priority: - normal
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5331
___
___
Python-bugs-list
New submission from mike bayer mike...@zzzcomputing.com:
this occurs for me running on Mac OSX Leopard. The equivalent code
using processing in python 2.5 works fine, which is how I found this
bug - my code hung when upgraded to 2.6.Basically initiating a
multiprocessing.Pool inside of
David W. Lambert lamber...@corning.com added the comment:
Fails also on this system.
$ p3
Python 3.0.1 (r301:69556, Feb 13 2009, 23:52:55)
[GCC 3.4.6 20060404 (Red Hat 3.4.6-3)] on linux2
(...)
# use both hangs
(...)
p.start()
p.join()
(hmm la do diii laaa...)^C
Traceback (most recent
Changes by Benjamin Peterson benja...@python.org:
--
assignee: - jnoller
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5331
___
