Коренберг Марк

https://gist.github.com/nathan-hoad/8966377 - is it good ? @vxgmichel

I'm vote on implementing stream wrappers for generic file objects. Something like simple and stupid - `(reader, writer) = asyncio.wrap_fileobject(fileobj)` (use `fileobj.read()`, `fileobj.write()`, `fileobj.flush()` internally) - `(reader, writer) = asyncio.wrap_file_descriptor(fd)`...

@vxgmichel unfortunatelly, there are cases where file descriptor is pre-exist. For example, systemd's socket activation, or xinetd. Also, if stdout/stdin is pipe, input and output may block easily, so wrapping...

Yes, this need to be fixed. expansion of `bytearray` is very fast.

Yes, I can try. @1st1 can you provide the case where you notice performnce regression? (except this issue, since it already have performance test)

This test just hang on my PC... @frensjan can you compare preformance of your variant vs https://github.com/python/asyncio/pull/395 ?

Yes, I think `read_into` and `read_into_exactly` is good API.

The difference between `.read()` and `.readinto()` is only in which buffer is passed to kernel - either internal (like `stream._buffer`) or user-specified (that is passed as argument to `readinto`). So,...

Hm. I did not work on this. Someone should choose a way of solving this issue.

Well. I do not understand what you mean as "outside". Anyway, too broad permission is a security bug. If appliation is restarted, UNIX-socket is recreated (re-bound) and this code will...