Add a separate NEWS entry for a change to PyObject_CallMethod in the PEP 380 patch, and make the private CallMethod variants consistent with the public one

This commit is contained in:
Nick Coghlan 2012-01-14 16:45:48 +10:00
parent 76e1bb0ef9
commit 138f4656e3
2 changed files with 3 additions and 2 deletions

View File

@ -2449,6 +2449,9 @@ Library
C-API
-----
- PyObject_CallMethod now passes along any underlying AttributeError from
PyObject_GetAttr, instead of replacing it with something less informative
- Issue #10913: Deprecate misleading functions PyEval_AcquireLock() and
PyEval_ReleaseLock(). The thread-state aware APIs should be used instead.

View File

@ -2288,7 +2288,6 @@ _PyObject_CallMethodId(PyObject *o, _Py_Identifier *name, char *format, ...)
func = _PyObject_GetAttrId(o, name);
if (func == NULL) {
PyErr_SetString(PyExc_AttributeError, name->string);
return 0;
}
@ -2330,7 +2329,6 @@ _PyObject_CallMethodId_SizeT(PyObject *o, _Py_Identifier *name, char *format, ..
func = _PyObject_GetAttrId(o, name);
if (func == NULL) {
PyErr_SetString(PyExc_AttributeError, name->string);
return NULL;
}
va_start(va, format);