[Guido] >>> Hm, I thought it was explicitly the case that only (the statically >>> linked part of) the core would ever use these macros. So why would >>> there be 3rd party code breakage? [Neil] >> Nope, that was never the case, AFAIK. [Guido] > Sigh, I must've been confused by some other set of macros that had > this property. :-( The PyMem_XXX macros "(do) not preserve binary compatibility accross [sic] Python versions and (are) therefore deprecated in extension modules" is as close as we get to restricting any of these guys to the core. Similar text doesn't appear in the PyObject_XXX docs. That doesn't mean it wasn't intended, though <wink>.
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