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-April/022061.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 APIMartin v. Loewis martin@v.loewis.de
01 Apr 2002 09:47:55 +0200
Tim Peters <tim.one@comcast.net> writes:

> [martin@v.loewis.de]
> > The third part is easy to answer. If it is deprecated, and used in the
> > core or an extension, that use must be removed. 
> 
> This is too easy of an answer, as the docs *already* make such distinctions.
> Read the tail end of the PyMem_ docs (PyMem_UPPERCASE is supposedly already
> deprecated, but only in extension modules).

There is something wrong here, then. The author of this documentation
clearly meant that they are *internal*, and thus should have been
called _PyMem_UPPERCASE.

I'd be in favour of renaming them, thus actively breaking extension
modules that use them at compile time.

Regards,
Martin



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