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 arigo
Recipients amaury.forgeotdarc, arigo, fijal, loewis, theller
Date 2008-06-06.11:07:03
SpamBayes Score 0.10870954
Marked as misclassified No
Message-id <>
> (Another note: the C-level errno and the TLS copy should also be
> synchronized when the C code invokes a Python callback.)

What I meant is what should occur when a pure Python function is used
as a callback.  At this point there is already some logic e.g. to
re-acquire the GIL if necessary.  Maybe it needs to grow logic to
optionally copy the C-level errno into the TLS variable at the start,
and at the end copy it back into the C-level errno at the end, for the
cases where the C code expects the callback to be able to set errno.
Date User Action Args
2008-06-06 11:07:07arigosetspambayes_score: 0.10871 -> 0.10870954
recipients: + arigo, loewis, theller, amaury.forgeotdarc, fijal
2008-06-06 11:07:06arigosetspambayes_score: 0.10871 -> 0.10871
messageid: <>
2008-06-06 11:07:05arigolinkissue1798 messages
2008-06-06 11:07:03arigocreate