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/2003-March/033993.html below:

[Python-Dev] PyObject_New vs PyObject_NEW

[Python-Dev] PyObject_New vs PyObject_NEW [Python-Dev] PyObject_New vs PyObject_NEWTim Peters tim.one@comcast.net
Wed, 12 Mar 2003 14:26:22 -0500
[David Abrahams]
> ...
> It seems to me that in light of all this, it's probably worth noting
> this difference between PyObject_New and PyObject_NEW in the docs.

I don't think the macro versions should ever be used outside the core.
Inside the core, it's safe.  So I think the "doc bug" is that the docs
mention PyObject_NEW at all.

> People *will* develop extension modules with different compilers from
> the one Python was compiled with...

Yup.

> I know, submit a patch.

That would be a sociable thing.




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