Message 300945 - 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	vstinner
Recipients	serhiy.storchaka, vstinner, xiang.zhang
Date	2017-08-28.09:32:53
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<CAMpsgwZXzh_g558hfzAm0-q4A_xGaLb8AYvW3X+DNM_ySfMjng@mail.gmail.com>
In-reply-to	<1503896496.88.0.68083436989.issue31282@psf.upfronthosting.co.za>

Content
You must hold the GIL to call PyMem_Malloc(). A debug assert should be raised if you don't hold the GIL since Python 3.6 with PYTHONMALLOC=debug. Call PyMem_RawMalloc(). I fixed Python 3, no? For Python 2, in practice you can call PyMem_Malloc() without holding the GIL, it's just malloc() which is thread safe.

You must hold the GIL to call PyMem_Malloc(). A debug assert should be
raised if you don't hold the GIL since Python 3.6 with PYTHONMALLOC=debug.

Call PyMem_RawMalloc().

I fixed Python 3, no?

For Python 2, in practice you can call PyMem_Malloc() without holding the
GIL, it's just malloc() which is thread safe.

History
Date	User	Action	Args
2017-08-28 09:32:53	vstinner	set	recipients: + vstinner, serhiy.storchaka, xiang.zhang
2017-08-28 09:32:53	vstinner	link	issue31282 messages
2017-08-28 09:32:53	vstinner	create