[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

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 of

[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

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 __

[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

Alexander Myodov 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 probably a Windows oof

[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

Brian Curtin added the comment: Can you provide a test case for this? -- nosy: +asksol, brian.curtin stage: -> unit test needed ___ Python tracker ___ __

[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

Changes by R. David Murray : -- nosy: +jnoller ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue9099] multiprocessing/win32: WindowsError: [Error 0] Success on Pipe()

Alexander Myodov 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: win32