I'm confident that you *can* write working code using the low-level API (event loop methods, possibly writing a custom protocol, which isn't verboten). Yes, it will be complicated (as the discussion in this thread has shown), but once someone figures it out it can live for a long time as a recipe or PyPI package. We can add it to the stdlib in 3.5.
On Wed, Feb 19, 2014 at 7:46 AM, Jonathan Slenders < [email protected]> wrote: > Late reply, but two-way pipe transport or something that feels like a > better API would be really nice. > There will be more people that are going to try asynchronous stdin/stdout > operations. > > Honestly, I'm not sure that I have the time myself to write a patch... > > > > Le mercredi 12 février 2014 19:29:28 UTC+1, Guido van Rossum a écrit : > >> I wonder if we shouldn't have a separate concept of a two-way pipe >> transport in UNIX? It's clear that the write-only pipe implementation >> doesn't work when the pipe is also readable. >> >> -- >> --Guido van Rossum (python.org/~guido) >> > -- --Guido van Rossum (python.org/~guido)
