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/022025.html below:

[Python-Dev] Moving forward on the object memory API

[Python-Dev] Moving forward on the object memory API [Python-Dev] Moving forward on the object memory APIGuido van Rossum guido@python.org
Sun, 31 Mar 2002 16:26:42 -0500
> Note that Guido recently reported:
> 
>     The memory thus allocated is returned by PyOS_Readline() (which calls
>     either function through a hook pointer), and both its callers (the
>     tokenizer and raw_input()) free the result using PyMem_DEL or
>     PyMem_FREE (these two seem to be used synonymically).
> 
> If that's so, PyMem_DEL and PyMem_FREE should be the same (but that grates
> on me too, FWIW).

I'd be happy to clean up the PyOS_Readline mess, which IMO is unique
in the Python core (one of the *very* few spots I know of that
allocates memory without the GIL).

> I think ultimately has to come from Guido, but the best way to get
> that to happen is to provoke him with schemes he doesn't like <wink>.

I prefer to sit down with you and go over this systematically.  The
asynchrony of email (and my lack of attention span when reading email
while watching Orlijn) makes it hard to do a good job in email.

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



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