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 pitrou
Recipients amaury.forgeotdarc, arigo, ghaering, jcea, pitrou, pxd
Date 2012-06-28.17:40:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1340905152.3379.8.camel@localhost.localdomain>
In-reply-to <1340904970.5.0.248320618591.issue15108@psf.upfronthosting.co.za>
Content
> Are there any guidelines on when GIL should be released?

The GIL should be released:
- for CPU-heavy external functions (e.g. compression, cryptography)
- for external functions which wait for I/O

> Re PyTuple_SET_ITEM...yes that's also a possibility but it would then
> hide genuine bugs.

Well, as long as your monitor only increfs the tuple and doesn't mutate
it, there shouldn't be any problem. We use PyTuple_SET_ITEM in many
other places.
History
Date User Action Args
2012-06-28 17:40:06pitrousetrecipients: + pitrou, arigo, jcea, ghaering, amaury.forgeotdarc, pxd
2012-06-28 17:40:06pitroulinkissue15108 messages
2012-06-28 17:40:05pitroucreate