AFAIK that buffer size is passed to the *io* stream created by subprocess.py. But we don't use that object at all, except to call fileno() to get its FD. So I think it should always be left zero. (I thought I even had an assert for that, but I can't find it now.)
On Tue, Jan 28, 2014 at 3:50 PM, Andrew Svetlov <[email protected]>wrote: > I had disabled buffering by default in first implementation to get > simple and clean design. > Do you think double buffering in transport/protocol and subprocess > itself is safe? > > On Wed, Jan 29, 2014 at 1:42 AM, Victor Stinner > <[email protected]> wrote: > > Hi, > > > > Does it make sense to use buffered pipes for a child process with Tulip? > > > > I see that BaseEventLoop.subprocess_exec/_shell sets bufsize to 0 by > > default. But I would like to know if Tulip supports buffered pipes and > > if it makes sense. > > > > Victor > > > > -- > Thanks, > Andrew Svetlov > -- --Guido van Rossum (python.org/~guido)
