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 Fulvio Esposito
Recipients Fulvio Esposito, gvanrossum, vstinner, yselivanov
Date 2016-04-21.17:34:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1461260041.01.0.731551553745.issue26819@psf.upfronthosting.co.za>
In-reply-to
Content
Calling pause_reading()/resume_reading() on a _ProactorReadPipeTransport will result in an InvalidStateError('Result is not ready.') from a future if no read has been issued yet. The reason is that resume_reading() will schedule _loop_reading() a second time on the event loop. For example, currently aiomysql always fails to connect using a ProactorEventLoop on Windows because it calls pause_reading()/resume_reading() to set TCP_NODELAY on the socket just after connecting and before any read is performed.
History
Date User Action Args
2016-04-21 17:34:01Fulvio Espositosetrecipients: + Fulvio Esposito, gvanrossum, vstinner, yselivanov
2016-04-21 17:34:01Fulvio Espositosetmessageid: <1461260041.01.0.731551553745.issue26819@psf.upfronthosting.co.za>
2016-04-21 17:34:00Fulvio Espositolinkissue26819 messages
2016-04-21 17:34:00Fulvio Espositocreate