[Python-Dev] Modify PyMem_Malloc to use pymalloc for performance (original) (raw)
Victor Stinner victor.stinner at gmail.com
Mon Feb 8 09:21:25 EST 2016
- Previous message (by thread): [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance
- Next message (by thread): [Python-Dev] Git for Mercurial Users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2016-02-07 9:22 GMT+01:00 Stefan Behnel <stefan_ml at behnel.de>:
Note that the PyObjectMalloc() functions have never been documented.
Yeah, there is an old bug to track this: http://bugs.python.org/issue20064
And, for example, the "what's new in 2.5" document says:
""" Python’s API has many different functions for allocating memory that are grouped into families. For example, PyMemMalloc(), PyMemRealloc(), and PyMemFree() are one family that allocates raw memory, while PyObjectMalloc(), PyObjectRealloc(), and PyObjectFree() are another family that’s supposed to be used for creating Python objects. """ I don't think there are many extensions out there in which object memory gets allocated manually, which implicitly puts a pretty clear "don't use" marker on these functions.
Should I understand that it's another good reason to make PyMem_Malloc() faster for everyone?
Victor
- Previous message (by thread): [Python-Dev] Modify PyMem_Malloc to use pymalloc for performance
- Next message (by thread): [Python-Dev] Git for Mercurial Users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]