Message220923
> I'm surprised that the Python read() method doesn't handle EINTR internally.
>
> I'm in favor of handling EINTR internally almost everywhere, I mean in the Python modules implemented in the C, not in each call using these C methods. "handling EINTR" means calling PyErr_CheckSignals() which may raises a Python exception (ex: KeyboardInterrupt).
It's good, we all agree on that.
I think the different EINTR-related reports should be closed as #18885
duplicates.
Then we need a patch for #18885: my idea was to write a pair of macros
similar to Py_BEGIN_ALLOW_THREADS/Py_END_ALLOW_THREADS that would
handle the retry logic, instead of having to check for EINTR and
calling Py_CheckPendingSignals() everywhere. |
|
Date |
User |
Action |
Args |
2014-06-18 07:03:01 | neologix | set | recipients:
+ neologix, lemburg, vstinner, Tor.Colvin |
2014-06-18 07:03:01 | neologix | link | issue21772 messages |
2014-06-18 07:03:01 | neologix | create | |
|