Message78164
On Sun, Dec 21, 2008 at 9:52 PM, Martin v. Löwis <report@bugs.python.org> wrote:
>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
>> It isn't being careful when calling PyErr_SetFromErrno inside the
>> Py_UniversalNewlineFread function since this function is being called
>> all over fileobject after releasing the GIL.. so, isn't this just a
>> matter of adding pairs of PyGILState_Ensure/PyGILState_Release around
>> these calls to PyErr_SetFromErrno in this specific function ?
>
> Perhaps that could fix this problem (or perhaps not - is
> PyGILState_Ensure guaranteed to do the right thing, even in the
> presence of multiple interpreters?)
It is said to be unsupported in that case, but I guess you knew that. |
|
Date |
User |
Action |
Args |
2008-12-21 23:55:26 | gpolo | set | recipients:
+ gpolo, loewis, belopolsky, josm |
2008-12-21 23:55:25 | gpolo | link | issue1706039 messages |
2008-12-21 23:55:25 | gpolo | create | |
|