[Python-Dev] Activating pymalloc (original) (raw)

Martin v. Loewis martin@v.loewis.de
25 Mar 2002 13:39:38 +0100

Tim Peters <tim.one@comcast.net> writes:

One simplification: deprecate the entire PyObjectXXX family. We introduced PyMallocXXX to do what PyObjectXXX was supposed to be used for; it's "only" backward compatibility that argued for introducing PyMallocXXX instead. OTOH, deprecating PyObjectXXX isn't a simplification extension authors are likely to appreciate at first .

+1. IMO, deprecation would involve removing those from the documentation (or explicitly list them as deprecated, without explaining what they do), and explain that they are dead in the header files. That could be the state of deprecation for the years to come.

Extension authors won't appreciate the introduction of PyMalloc_*, since it means they need to change their code to make use of the pool allocator, but once they've done that, there should not be any PyObject_ left in your code.

Regards, Martin