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

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

[Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?

• Previous message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
• Next message: [Python-Dev] generalized resource alloc and de-alloc
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Skip Montanaro wrote:
> Neil S. reported on a number of 3rd party extension modules that don't do
> object alloc/free properly.  I reported a bug to the mysql-python project,
> which uses PyObject_NEW and PyMem_Free.  Andy Dustman's reply, in part, was:
> 
>     1.5.2 apparently does not have PyObject_New() or PyObject_Del(), thus
>     the problem...

I don't consider extension modules that use PyObject_NEW and PyMem_DEL
broken.  The used to be the recommended way of doing it.  We can't
change that until at least Python 3.0.

  Neil

• Previous message: [Python-Dev] pymalloc API - is 1.5.2 compatibility a possible explanation?
• Next message: [Python-Dev] generalized resource alloc and de-alloc
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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