➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jcea
Recipients brett.cannon, eric.smith, eric.snow, gregory.p.smith, jcea, ncoghlan, python-dev, twouters
Date 2012-04-19.00:03:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1334793785.23.0.482570207994.issue14331@psf.upfronthosting.co.za>
In-reply-to
Content 
"PyErr_NoMemory()" returns always NULL, but it is declared as returning "PyObject *".

Could we change "return PyErr_NoMemory();" to "PyErr_NoMemory(); return NULL;"?. Maybe with some comment... A cast would silence the compiler but could be unclear. What do you think?

This is not a problem in 3.2 because the function patched returns a "PyObject *".
History
Date User Action Args
2012-04-19 00:03:05jceasetrecipients: + jcea, twouters, brett.cannon, gregory.p.smith, ncoghlan, eric.smith, python-dev, eric.snow
2012-04-19 00:03:05jceasetmessageid: <1334793785.23.0.482570207994.issue14331@psf.upfronthosting.co.za>
2012-04-19 00:03:04jcealinkissue14331 messages
2012-04-19 00:03:04jceacreate