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 hfuru
Recipients hfuru
Date 2010-11-08.08:48:15
SpamBayes Score 4.5188236e-10
Marked as misclassified No
Message-id <>
errno is sometimes read too late after the error:  After another call
may have modified it.  Here's a patch against py3k.  Most of it or a
variant applies to 2.7 too, but I haven't really looked at that.

I've not looked at math code, where I don't even know what sets errno.

There might also be a late errno read at Modules/_ctypes/callproc.c
line 794: "space[0] = errno;".  Does it want the errno from before
_ctypes_get_errobj()?  I'm unsure what's going on there.

Modules/_multiprocessing/semaphore.c doesn't need the patch's extra
variable, it can instead be rearranged with the commented-out patch.
Date User Action Args
2010-11-08 08:48:18hfurusetrecipients: + hfuru
2010-11-08 08:48:18hfurusetmessageid: <>
2010-11-08 08:48:17hfurulinkissue10350 messages
2010-11-08 08:48:16hfurucreate