Message 251592 - Python tracker

➜

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	rhettinger
Recipients	rhettinger, serhiy.storchaka, vstinner
Date	2015-09-25.18:15:10
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1443204910.97.0.772289076274.issue25135@psf.upfronthosting.co.za>
In-reply-to

Content
> I'm not sure that you understand what you are trying to do. The goal is to avoid possible re-entrancy both now and in the future. Since PyMem_RawMalloc is thread-safe and doesn't require the GIL to be held, it is guaranteed that there won't be a callback into regular Python that could mutate any of the data structures.

> I'm not sure that you understand what you are trying to do.

The goal is to avoid possible re-entrancy both now and in the future.  Since PyMem_RawMalloc is thread-safe and doesn't require the GIL to be held, it is guaranteed that there won't be a callback into regular Python that could mutate any of the data structures.

History
Date	User	Action	Args
2015-09-25 18:15:11	rhettinger	set	recipients: + rhettinger, vstinner, serhiy.storchaka
2015-09-25 18:15:10	rhettinger	set	messageid: <1443204910.97.0.772289076274.issue25135@psf.upfronthosting.co.za>
2015-09-25 18:15:10	rhettinger	link	issue25135 messages
2015-09-25 18:15:10	rhettinger	create