CObject use is marked as a Py3k warning, not a deprecation warning

This commit is contained in:
Jesus Cea 2010-11-04 21:39:52 +00:00
parent db31a35aa9
commit 33c722b795
2 changed files with 4 additions and 2 deletions

View File

@ -25,6 +25,9 @@ Core and Builtins
- Issue #9862: Compensate for broken PIPE_BUF in AIX by hard coding
its value as the default 512 when compiling on AIX.
- Issue #9675: CObject use is marked as a Py3k warning, not a deprecation
warning.
- Issue #10068: Global objects which have reference cycles with their module's
dict are now cleared again. This causes issue #7140 to appear again.

View File

@ -11,8 +11,7 @@ typedef void (*destructor2)(void *, void*);
static int cobject_deprecation_warning(void)
{
return PyErr_WarnEx(PyExc_PendingDeprecationWarning,
"The CObject type is marked Pending Deprecation in Python 2.7. "
return PyErr_WarnPy3k("CObject type is not supported in 3.x. "
"Please use capsule objects instead.", 1);
}