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 benjamin.peterson, gregory.p.smith, izbyshev, miss-islington, pitrou, serhiy.storchaka, siddhesh, skrah, steve.dower, vstinner
Date 2018-11-30.16:56:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1543596968.3.0.788709270274.issue33015@psf.upfronthosting.co.za>
In-reply-to
Content
I wrote PR 10828 to make PyMem_Malloc() thread-safe in debug mode as well.. But I'm not sure that it's ok to push such change later in the 2.7 development cycle...

So I wrote PR 10829 which only modified PyThread_start_new_thread(): use malloc/free instead of PyMem_Malloc/PyMem_Free.
History
Date User Action Args
2018-11-30 16:56:08vstinnersetrecipients: + vstinner, gregory.p.smith, pitrou, benjamin.peterson, skrah, serhiy.storchaka, steve.dower, siddhesh, izbyshev, miss-islington
2018-11-30 16:56:08vstinnersetmessageid: <1543596968.3.0.788709270274.issue33015@psf.upfronthosting.co.za>
2018-11-30 16:56:08vstinnerlinkissue33015 messages
2018-11-30 16:56:08vstinnercreate