[issue26270] Support for read()/write()/select() on asyncio

Change by Andrew Svetlov : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

[issue26270] Support for read()/write()/select() on asyncio

Andrew Svetlov added the comment: The suggestion is using streams as a high-level API. I see no real proposals in this issue. select()/read()/write() is not suitable interface, sorry. Closing, feel free to create a new issue if you come up with a concrete proposal. --

[issue26270] Support for read()/write()/select() on asyncio

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26270] Support for read()/write()/select() on asyncio

Change by Cheryl Sabella : -- nosy: +asvetlov versions: +Python 3.8 -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing

[issue26270] Support for read()/write()/select() on asyncio

Change by Guido van Rossum : -- nosy: -gvanrossum ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26270] Support for read()/write()/select() on asyncio

Change by smheidrich : -- nosy: +smheidrich ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26270] Support for read()/write()/select() on asyncio

Paulo Costa added the comment: Thanks for the replies. What I'm actually trying to do is to access from a character file from /dev/input/event*. Streams are pretty much what I want to use but (as far as I can tell) asyncio's streams only support network and unix sockets. Files are left

[issue26270] Support for read()/write()/select() on asyncio

STINNER Victor added the comment: > Anyway, despite the existence of streams and protocols, I still believe that > `asyncio.read()`, `asyncio.write()` and `asyncio.select()` would be > nice-to-have low-level APIs. You can probably develop your own helper functions based on existing asyncio

[issue26270] Support for read()/write()/select() on asyncio

Guido van Rossum added the comment: Regular are left behind because select() won't work on them. However we do support certain file descriptors (e.g. pipes) and it makes sense to support device "files". Can you come up with a new API that lets you pass a file descriptor and wrap it in a

[issue26270] Support for read()/write()/select() on asyncio

STINNER Victor added the comment: Paulo Costa: > async def async_read(fd. n): This method already exists: * (TCP) https://docs.python.org/dev/library/asyncio-protocol.html#asyncio.Protocol.data_received * (UDP)

[issue26270] Support for read()/write()/select() on asyncio

New submission from Paulo Costa: I want to read from file descriptors from async coroutines. I currently use `loop.add_reader(fd, callback)` and `loop.remove_reader(fd)` It works, but IMO using callbacks feels completely alien in the middle of a coroutine. I suggest adding new APIs to handle

[issue26270] Support for read()/write()/select() on asyncio

Martin Panter added the comment: Maybe I misunderstand the asyncio protocols, transports, streams, etc too :) but last time I looked they all seemed to buffer your write data and send it in the background. E.g. in the echo-client-using-streams example, there is a writer.write() call that does