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 loewis
Recipients amaury.forgeotdarc, arigo, fijal, loewis, theller
Date 2008-05-23.17:34:21
SpamBayes Score 0.0017066373
Marked as misclassified No
Message-id <4837001B.5010908@v.loewis.de>
In-reply-to <1211558241.9.0.166872314709.issue1798@psf.upfronthosting.co.za>
Content
[...]
> 
> Using the native errno instead of a custom TLS value is bad because a
> lot of things can occur

So what's the semantics of set_errno then? Set the real errno? If so,
what if it gets changed between the call to set_errno, and the actual
invocation of API function? Set the TLS errno? If so, when does it get
copied into the real errno?
History
Date User Action Args
2008-05-23 17:34:23loewissetspambayes_score: 0.00170664 -> 0.0017066373
recipients: + loewis, arigo, theller, amaury.forgeotdarc, fijal
2008-05-23 17:34:22loewislinkissue1798 messages
2008-05-23 17:34:21loewiscreate