Author jeffr@livedata.com
Recipients asvetlov, jeffr@livedata.com, yselivanov
Date 2018-12-24.23:41:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1545694904.74.0.712150888896.issue35580@roundup.psfhosted.org>
In-reply-to
Content
By default, the __init__ function of IocpProactor in windows_events.py calls CreateIoCompletionPort with a 4th argument of 0xffffffff, yet MSDN doesn't document this as a valid argument.    https://docs.microsoft.com/en-us/windows/desktop/fileio/createiocompletionport

It looks like the 4th arg (NumberOfConcurrentThreads) is meant to be either a positive integer or 0.  0 is a special value meaning "If this parameter is zero, the system allows as many concurrently running threads as there are processors in the system."

Why does asyncio use 0xffffffff instead as the default value?
History
Date User Action Args
2018-12-24 23:41:48jeffr@livedata.comsetrecipients: + jeffr@livedata.com, asvetlov, yselivanov
2018-12-24 23:41:44jeffr@livedata.comsetmessageid: <1545694904.74.0.712150888896.issue35580@roundup.psfhosted.org>
2018-12-24 23:41:44jeffr@livedata.comlinkissue35580 messages
2018-12-24 23:41:44jeffr@livedata.comcreate