Author haypo
Recipients Yury.Selivanov, alecsandru.patrascu, catalin.manciu, haypo, jtaylor, pitrou, rhettinger, serhiy.storchaka, yselivanov
Date 2016-03-09.17:36:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwY3EJofDUPeVknLpnzsXRX6=CxF8jTZMwfsWvRwOn_YhA@mail.gmail.com>
In-reply-to <56E05D5A.3060404@free.fr>
Content
2016-03-09 18:28 GMT+01:00 Antoine Pitrou <report@bugs.python.org>:
> Does the API doc say anything about the GIL, for example? Or Valgrind?

For the GIL, yes, Python 3 doc is explicit:
https://docs.python.org/dev/c-api/memory.html#memory-interface

Red and bold warning: "The GIL must be held when using these functions."

Hum, sadly it looks like the warning miss in Python 2 doc.

The GIL was the motivation to introduce the PyMem_RawMalloc() function
in Python 3.4.

For Valgrind: using the issue #26516, you will be able to use
PYTHONMALLOC=malloc to use easily Valgrind even on a Python compiled
in release mode (which is a new feature, before you had to manually
recompile Python in debug mode with --with-valgrind)).
History
Date User Action Args
2016-03-09 17:36:03hayposetrecipients: + haypo, rhettinger, pitrou, Yury.Selivanov, jtaylor, serhiy.storchaka, yselivanov, alecsandru.patrascu, catalin.manciu
2016-03-09 17:36:02haypolinkissue26249 messages
2016-03-09 17:36:02haypocreate