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 jeffr@livedata.com
Recipients asvetlov, jeffr@livedata.com, vstinner, yselivanov
Date 2019-02-16.22:00:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550354408.88.0.612194192388.issue35580@roundup.psfhosted.org>
In-reply-to
Content
I don't understand why 0 would be safer.  Since asyncio can only service this IOCP from its single threaded event loop, I would have thought 1 would express the intent better.  

Why not convey to the OS what we're up to, in case that helps it do a better job or reduces resource footprint?
History
Date User Action Args
2019-02-16 22:00:08jeffr@livedata.comsetrecipients: + jeffr@livedata.com, vstinner, asvetlov, yselivanov
2019-02-16 22:00:08jeffr@livedata.comsetmessageid: <1550354408.88.0.612194192388.issue35580@roundup.psfhosted.org>
2019-02-16 22:00:08jeffr@livedata.comlinkissue35580 messages
2019-02-16 22:00:08jeffr@livedata.comcreate