[Python-Dev] pymalloc on Windows

[Guido van Rossum]

> > I assume from previous discussions here that _PyCore_ObjectMalloc
> > is indeed supposed to be private and not exposed from the main
> > module/dll.
> 
> That would break lots of code... basically all code using
> the macros instead of the functions, I guess.

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?

> > I have patches for both these modules.  However, I wonder if a more
> > pragmatic option is to expose this core function.  It would allow
> > PyObject_NEW to continue to work as before.
> 
> +1

-1.

--Guido van Rossum (home page: http://www.python.org/~guido/)