Message 308933 - 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	asvetlov
Recipients	asvetlov, jabdoa, yselivanov
Date	2017-12-22.13:23:30
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1513949010.45.0.213398074469.issue32396@psf.upfronthosting.co.za>
In-reply-to

Content
Looking on serial port support in twisted (https://github.com/twisted/twisted/blob/trunk/src/twisted/internet/_win32serialport.py) I see that it is implemented by OVERLAPPED structure and ReadFile/WriterFile calls. On other hand loop.sock_send() in ProactorEventLoop uses Proactor.send() (https://github.com/python/cpython/blob/master/Lib/asyncio/windows_events.py#L457). The method calls WriteFile is sock is not socket.socket instance. Did you check if `loop.sock_send()`/`loop.sock_recv()` works for serail port object?

Looking on serial port support in twisted (https://github.com/twisted/twisted/blob/trunk/src/twisted/internet/_win32serialport.py) I see that it is implemented by OVERLAPPED structure and ReadFile/WriterFile calls.

On other hand loop.sock_send() in ProactorEventLoop uses Proactor.send() (https://github.com/python/cpython/blob/master/Lib/asyncio/windows_events.py#L457).

The method calls WriteFile is sock is not socket.socket instance.

Did you check if `loop.sock_send()`/`loop.sock_recv()` works for serail port object?

History
Date	User	Action	Args
2017-12-22 13:23:30	asvetlov	set	recipients: + asvetlov, yselivanov, jabdoa
2017-12-22 13:23:30	asvetlov	set	messageid: <1513949010.45.0.213398074469.issue32396@psf.upfronthosting.co.za>
2017-12-22 13:23:30	asvetlov	link	issue32396 messages
2017-12-22 13:23:30	asvetlov	create