Tim Peters <tim.one@comcast.net> writes: > One simplification: deprecate the entire PyObject_XXX family. We > introduced PyMalloc_XXX to do what PyObject_XXX was *supposed* to be used > for; it's "only" backward compatibility that argued for introducing > PyMalloc_XXX instead. OTOH, deprecating PyObject_XXX isn't a simplification > extension authors are likely to appreciate at first <wink>. +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
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4