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 gpolo
Recipients belopolsky, gpolo, josm, loewis
Date 2008-12-21.23:55:25
SpamBayes Score 5.2516418e-05
Marked as misclassified No
Message-id <ac2200130812211555h6968fdb3ia3dcb9647675a6d1@mail.gmail.com>
In-reply-to <494ED6AA.9080609@v.loewis.de>
Content
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.
History
Date User Action Args
2008-12-21 23:55:26gpolosetrecipients: + gpolo, loewis, belopolsky, josm
2008-12-21 23:55:25gpololinkissue1706039 messages
2008-12-21 23:55:25gpolocreate