John Ehresman <j...@wingware.com> added the comment: Attached is a patch, though I have mixed feelings about it. The OS error can still occur even if a smaller amount is written in each WriteFile call; I think an internal OS buffer fills up and the error is returned if that buffer is full because the other process hasn't read yet. The patch just ignores ERROR_NO_SYSTEM_RESOURCES and writes again. I don't know though if ERROR_NO_SYSTEM_RESOURCES can mean something else is wrong and the write will never succeed. The message is also broken up into 32K parts and a recv_bytes on the other end must be called multiple times to read it all.
The patch is one option. Another might be to let the application decide to continue or not and essentially treat the pipes as nonblocking. ---------- keywords: +patch Added file: http://bugs.python.org/file13518/win32_pipe.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue3551> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
