classification
Title: Deprecate CObject
Type: behavior Stage:
Components: Interpreter Core Versions: Python 3.1
process
Status: closed Resolution: accepted
Dependencies: Superseder:
Assigned To: Nosy List: georg.brandl, larry
Priority: normal Keywords: patch

Created on 2009-05-05 23:45 by larry, last changed 2009-05-06 08:48 by georg.brandl. This issue is now closed.

Files
File name Uploaded Description Edit
lch.deprecatecobject.r72363.diff larry, 2009-05-05 23:45 Patch against py3k/trunk r72363.
lch.deprecatecobject.r72374.diff larry, 2009-05-06 07:48 Patch against py3k/trunk r72374.
Messages (3)
msg87302 - (view) Author: Larry Hastings (larry) * (Python committer) Date: 2009-05-05 23:45
With the Capsule API patch accepted, I'd like to officially deprecate
CObject.  This patch causes Python to emit a single runtime warning the
first time a CObject is constructed in a particular Python instance.  If
those aren't the right semantics for a deprecation warning, please let
me know and I'll fix it.
msg87316 - (view) Author: Larry Hastings (larry) * (Python committer) Date: 2009-05-06 07:48
It's 12:45am, and I've already learned my New Thing for the day.  I
didn't know about PendingDeprecationWarning.  That's just exactly what
CObject should throw.

Attached is a new patch.  The two CObject constructors now throw a
PendingDeprecationWarning every time they are called.

Tested manually: I create CObjects and nothing happens.  I then run
warnings.resetwarnings() and create CObjects and see a
PendingDeprecationWarning.  Perfect!
msg87324 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-05-06 08:48
Applied in r72397.
History
Date User Action Args
2009-05-06 08:48:06georg.brandlsetstatus: open -> closed

nosy: + georg.brandl
messages: + msg87324

resolution: accepted
2009-05-06 07:48:22larrysetfiles: + lch.deprecatecobject.r72374.diff

messages: + msg87316
2009-05-05 23:45:32larrycreate