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 kristjan.jonsson
Recipients alexis, brian.curtin, eric.araujo, jackjansen, kristjan.jonsson, loewis, mhammond, sable, santoso.wijaya, tarek, tim.golden, vstinner
Date 2012-03-31.18:30:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content
Why should python compiled with VS2010 have different error codes than one compiled with the older compilers?  We could revisit this in a new python version, but for now, we should maintain compatibility across compilers.

the errno codes (EAGAIN etc) are provided only as a compatibility for posix apps that test "errno".  On windows, we use the WSA return values from the api functions and WsaGetLastError().

The reason this patch is required is that now, the errno constants get pulled in with the WSA ones, and therefore the conditional compilation in errnomodule.c gets mangled.  So, the proposed patch is not a change, it is merely reinforcing the previous practice of prefering the native error codes over the 'errno' emulation.  Of course, this should be clarified in a comment, as you point out.
History
Date User Action Args
2012-03-31 18:30:42kristjan.jonssonsetrecipients: + kristjan.jonsson, loewis, mhammond, jackjansen, vstinner, sable, tim.golden, tarek, eric.araujo, brian.curtin, santoso.wijaya, alexis
2012-03-31 18:30:42kristjan.jonssonsetmessageid: <[email protected]>
2012-03-31 18:30:42kristjan.jonssonlinkissue13210 messages
2012-03-31 18:30:42kristjan.jonssoncreate