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:42:45
SpamBayes Score 0.020951351
Marked as misclassified No
Message-id <1229902969.15.0.878875875084.issue1706039@psf.upfronthosting.co.za>
In-reply-to
Content
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 ?
History
Date User Action Args
2008-12-21 23:42:49gpolosetrecipients: + gpolo, loewis, belopolsky, josm
2008-12-21 23:42:49gpolosetmessageid: <1229902969.15.0.878875875084.issue1706039@psf.upfronthosting.co.za>
2008-12-21 23:42:45gpololinkissue1706039 messages
2008-12-21 23:42:45gpolocreate