Message 308869 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	jabdoa
Recipients	asvetlov, jabdoa, yselivanov
Date	2017-12-21.12:42:09
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1513860129.41.0.213398074469.issue32396@psf.upfronthosting.co.za>
In-reply-to

Content
This is a follow up to Issue30539. The main issue is that serial ports on windows do not behave like socket on unix. Therefore, pyserial-asyncio cannot use the asyncio socket api. Can we implement serial_recv and serial_send in asyncio? This would help to create a true platform independent implementation. On Linux and Mac serial_send/recv could probably just call to socket_sendall/recv. On Windows this would map to ProactorEventLoop.send/recv.

This is a follow up to Issue30539. The main issue is that serial ports on windows do not behave like socket on unix. Therefore, pyserial-asyncio cannot use the asyncio socket api.

Can we implement serial_recv and serial_send in asyncio? This would help to create a true platform independent implementation. On Linux and Mac serial_send/recv could probably just call to socket_sendall/recv. On Windows this would map to ProactorEventLoop.send/recv.

History
Date	User	Action	Args
2017-12-21 12:42:09	jabdoa	set	recipients: + jabdoa, asvetlov, yselivanov
2017-12-21 12:42:09	jabdoa	set	messageid: <1513860129.41.0.213398074469.issue32396@psf.upfronthosting.co.za>
2017-12-21 12:42:09	jabdoa	link	issue32396 messages
2017-12-21 12:42:09	jabdoa	create