Author marc@bruenink.de
Recipients BreamoreBoy, Marc.Brünink, docs@python, eryksun, marc@bruenink.de
Date 2014-06-20.06:47:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403246842.93.0.547226561975.issue18017@psf.upfronthosting.co.za>
In-reply-to
Content
I think the problem was a combination of two issues.

First, the warning in 16.17.2.2 is a bit hidden. Kind of squeezed in 
between CDLL, etc and PyDLL. In contrast, 16.17.2.4 does a much better 
job, because it restates the fact that the GIL is released at each and 
every item. I think this is much better, because chances are high that 
you actually read the entry completely. In contrast, in case you 
are in a hurry you might miss the warning in 16.17.2.2

I think the second problem was that back then I was not aware of the 
fact that you need the GIL to call the Python/C API. That was a bit 
stupid indeed. But as a Python beginner it was just not obvious. Maybe 
the Introduction of the Python/C API needs some work, too. No GIL 
mentioned at https://docs.python.org/3/c-api/intro.html.
Furthermore, the examples at 
https://docs.python.org/3/extending/extending.html also do not talk 
about the GIL.
History
Date User Action Args
2014-06-20 06:47:22marc@bruenink.desetrecipients: + marc@bruenink.de, docs@python, BreamoreBoy, eryksun, Marc.Brünink
2014-06-20 06:47:22marc@bruenink.desetmessageid: <1403246842.93.0.547226561975.issue18017@psf.upfronthosting.co.za>
2014-06-20 06:47:22marc@bruenink.delinkissue18017 messages
2014-06-20 06:47:22marc@bruenink.decreate