Message120479
| Author |
hfuru |
| Recipients |
amaury.forgeotdarc, exarkun, hfuru, loewis, pitrou |
| Date |
2010年11月05日.09:49:55 |
| SpamBayes Score |
3.4364356e-10 |
| Marked as misclassified |
No |
| Message-id |
<hbf.20101105jw67@bombur.uio.no> |
| In-reply-to |
<1288882537.9.0.304460920785.issue10311@psf.upfronthosting.co.za> |
| Content |
Antoine Pitrou writes:
> By the way, I'd like to clear out a potential misunderstanding: the
> function you are patching doesn't call Python signal handlers in itself
> (those registered using signal.signal()). (...)
Good point - I'm talking C signal handlers, not Python signal handlers.
> If you want to save errno around Python signal handlers
> themselves, PyErr_CheckSignals must be patched as well.
Probably not. I don't know Python's errno conventions, if any, but
it's usually a bug to use errno at any distance from the error. The C
code near the error can save errno if it wants it later. It can't do
that around C signal handlers, since those can get called anywhere. |
|