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 pitrou
Recipients amaury.forgeotdarc, exarkun, hfuru, loewis, pitrou
Date 2010-11-04.14:50:06
SpamBayes Score 5.599232e-05
Marked as misclassified No
Message-id <1288882208.61.0.379860480119.issue10311@psf.upfronthosting.co.za>
In-reply-to
Content
> ["this" = only saving/restoring errno when needed]
> True, but practically nothing is officially safe to do in signal
> handlers, so it's good to avoid code which can be avoided there.
> If one can be bothered to, that is.

I think it is extremely unlikely that mutating errno in a signal handler is unsafe (after all, the library functions called from that handler can mutate errno too: that's the whole point of the patch IIUC). Adding some configure machinery for this seems unwarranted to me.
History
Date User Action Args
2010-11-04 14:50:08pitrousetrecipients: + pitrou, loewis, exarkun, amaury.forgeotdarc, hfuru
2010-11-04 14:50:08pitrousetmessageid: <1288882208.61.0.379860480119.issue10311@psf.upfronthosting.co.za>
2010-11-04 14:50:06pitroulinkissue10311 messages
2010-11-04 14:50:06pitroucreate