Author John Isidore
Recipients John Isidore, docs@python, gvanrossum
Date 2014-05-08.19:05:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1399575906.07.0.344601032189.issue21454@psf.upfronthosting.co.za>
In-reply-to
Content
the documentation for BaseEventLoop.connect_read_pipe says: 

> "pipe is file-like object **already switched** to nonblocking."

http://hg.python.org/cpython/file/232938736a31/Doc/library/asyncio-eventloop.rst#l453

But it looks like connect_read_pipe() accepts blocking pipes and switches
them to non-blocking mode:

> "It looks like connect_read_pipe() (eventually) sets the fd to non-blocking. So it does work."

https://code.google.com/p/tulip/source/detail?r=0a716436176993a12cf861b6cafffe8a31bc1127

If it is indeed the case then the documentation should mention that it
accepts blocking pipes and makes them non-blocking.

May it break other processes by making the file non-blocking if it is a pty
that is shared between processes? 

Related: "Don't set shared file descriptors to non-blocking I/O mode."
http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/dont-set-shared-file-descriptors-to-non-blocking-mode.html
History
Date User Action Args
2014-05-08 19:05:06John Isidoresetrecipients: + John Isidore, gvanrossum, docs@python
2014-05-08 19:05:06John Isidoresetmessageid: <1399575906.07.0.344601032189.issue21454@psf.upfronthosting.co.za>
2014-05-08 19:05:05John Isidorelinkissue21454 messages
2014-05-08 19:05:03John Isidorecreate