homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author sbt
Recipients pitrou, sbt
Date 2012年05月05日.17:37:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336239485.69.0.802465792516.issue14725@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation page for ConnectNamedPipe (http://msdn.microsoft.com/en-us/library/windows/desktop/aa365146(v=vs.85).aspx) has a "community addition" which says that ConnectNamedPipe will appear to fail with ERROR_NO_DATA (232) if a client has previously connected, written some data and disconnected.
That seems to be what is happening. For example
 Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32
 Type "help", "copyright", "credits" or "license" for more information.
 >>> import multiprocessing.connection as con
 >>> l = con.Listener()
 >>> c = con.Client(l.address)
 >>> c.send("hello")
 >>> c.close()
 >>> l.accept()
 Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "c:\Python27\lib\multiprocessing\connection.py", line 145, in accept
 c = self._listener.accept()
 File "c:\Python27\lib\multiprocessing\connection.py", line 345, in accept
 win32.ConnectNamedPipe(handle, win32.NULL)
 WindowsError: [Error 232] The pipe is being closed
I will look in to it. The community addition says to just treat ERROR_NO_DATA as success.
History
Date User Action Args
2012年05月05日 17:38:05sbtsetrecipients: + sbt, pitrou
2012年05月05日 17:38:05sbtsetmessageid: <1336239485.69.0.802465792516.issue14725@psf.upfronthosting.co.za>
2012年05月05日 17:37:54sbtlinkissue14725 messages
2012年05月05日 17:37:54sbtcreate

AltStyle によって変換されたページ (->オリジナル) /