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 steve.dower
Recipients eryksun, paul.moore, steve.dower, tim.golden, zach.ware
Date 2019-08-26.17:49:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566841780.64.0.0793880113786.issue37705@roundup.psfhosted.org>
In-reply-to
Content
While I'm inclined to think it's okay to find the CRT sources (e.g. "C:\Program Files (x86)\Windows Kits\10\Source\10.0.18362.0\ucrt\misc\errno.cpp") and extract the table from there as part of build, the problem I have is that it is woefully incomplete.

I'd much rather have a manually managed table. It'd also be nice to expose it through the errno module somehow, probably just as a dict.

It also seems like at least some of the WSA* constants (e.g. WSAEBADF==10009) are the equivalent errno plus 10000 (e.g.EBADF==9). Should we be mapping those back to the errno value?
History
Date User Action Args
2019-08-26 17:49:40steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, zach.ware, eryksun
2019-08-26 17:49:40steve.dowersetmessageid: <1566841780.64.0.0793880113786.issue37705@roundup.psfhosted.org>
2019-08-26 17:49:40steve.dowerlinkissue37705 messages
2019-08-26 17:49:40steve.dowercreate