commit | 6e08c1460c79962a98e106437a089d2fe306403c | [log] [tgz] |
---|---|---|
author | Guido van Rossum <guido@python.org> | Fri Oct 11 20:37:24 2002 +0000 |
committer | Guido van Rossum <guido@python.org> | Fri Oct 11 20:37:24 2002 +0000 |
tree | 4cfee2618b8054f0522ec43dfd458828e6e3f389 | |
parent | c78462fb94b15d71c0dbfa6f3dfc2fabd29f635f [diff] |
PyObject_Init[Var] is almost always called from the PyObject_NEW[_VAR] macros. The 'op' argument is then the result from PyObject_MALLOC, and that can of course be NULL. In that case, PyObject_Init[Var] would raise a SystemError with "NULL object passed to PyObject_Init[Var]". But there's nothing the caller of the macro can do about this. So PyObject_Init[Var] should call just PyErr_NoMemory. Will backport.