Davin Potts added the comment:
Though the code may have changed a bit in the meantime (Issue11750 in
particular), the calls to _winapi.SetNamedPipeHandleState in
Lib/multiprocessing/connection.py are still present and largely the same as
when this issue was first opened.
The implementation
Mark Lawrence added the comment:
I'm not sure how we take this forward as the code was changed via #11750, can
somebody please advise.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9099
Changes by Brian Curtin br...@python.org:
--
nosy: -brian.curtin
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9099
___
___
Python-bugs-list
Alexander Myodov amyo...@gmail.com added the comment:
Sorry for being a little bit slow to respond...
No I was not able to come up with a testcase that could generate this problem
in a reproducible way on any Windows box I had. This problem sometimes occured
on various OS versions, being
Brian Curtin cur...@acm.org added the comment:
Can you provide a test case for this?
--
nosy: +asksol, brian.curtin
stage: - unit test needed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9099
New submission from Alexander Myodov amyo...@gmail.com:
I am using Python 2.6.5/win32, and working with multiprocessing module, doing
that with Python interpreter embedded using Cython (if that may be related to
the problem).
While creating a subprocess and a Pipe to communicate with it, I've
Alexander Myodov amyo...@gmail.com added the comment:
Sorry for formatting above, a copypaste issue.
The lines 202-204:
win32.SetNamedPipeHandleState(
h2, win32.PIPE_READMODE_MESSAGE, None, None
)
The change that fixes the problem (at least for me):
try:
Changes by R. David Murray rdmur...@bitdance.com:
--
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9099
___
___
Python-bugs-list
