A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2002-March/021332.html below:

[Python-Dev] pymalloc on Windows

[Python-Dev] pymalloc on WindowsM.-A. Lemburg mal@lemburg.com
Mon, 18 Mar 2002 15:00:23 +0100
Mark Hammond wrote:
> 
> It appears that the _sre and _winreg modules fail to build with
> WITH_PYMALLOC defined.
> 
> Both are extension modules, and both use the macro versions of the memory
> allocator functions - ie, PyObject_NEW etc.
> 
> Both fail at link time with, eg:
> 
> _winreg.obj : error LNK2001: unresolved external symbol
> __PyCore_ObjectMalloc
> 
> 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.
 
> 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

-- 
Marc-Andre Lemburg
CEO eGenix.com Software GmbH
______________________________________________________________________
Company & Consulting:                           http://www.egenix.com/
Python Software:                   http://www.egenix.com/files/python/



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