Guilherme Polo <ggp...@gmail.com> added the comment: On Sun, Dec 21, 2008 at 9:52 PM, Martin v. Löwis <rep...@bugs.python.org> wrote: > > Martin v. Löwis <mar...@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. _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue1706039> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
