[Python-Dev] API deprecations in Python 3, from a Python 2 perspective

Jesus Cea jcea at jcea.es
Fri Mar 18 19:20:18 CET 2011


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 18/03/11 01:01, Larry Hastings wrote:
> In 2.7.1 PyCObject_FromVoidPtr() now calls PyErr_WarnPy3k().  This means
> it's been promoted to throwing DeprecationWarning!  But that's also
> guarded with Py_Py3kWarningFlag so it's not active unless you ask for
> that too (as with "-3" on the command-line, etc).

I kind of remember doing this change myself. Since no 2.8 is planned, it
seemed sensible to mark PyCObject as a py3k warning.

PS: I am the maintainer of (externally developed lib) bsddb, but the
2.7.0 behaviour actually broke some other extensions out there (when
used with warnings active). Details in the tracker, somewhere. I am
offline now, can't use the browser.

- -- 
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea at jcea.es - http://www.jcea.es/     _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea at jabber.org         _/_/    _/_/          _/_/_/_/_/
.                              _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQCVAwUBTYOiYplgi5GaxT1NAQLtRgQAjdB1yvFmqJLGqqzEaCK+ll5jx277b751
RGshITBFUkd+OLVErP9nEKUMsHvr/nl7BIjhZotKH31g6Hl0KiuGPHHkPNKYGs4y
5XsHaZ2a9/qkgt1wa12gLsHmxsrIICGKPzcPUQs6GVJGBuppGtDkc18iODOCd6eC
kkDcc/sFHUI=
=mXiX
-----END PGP SIGNATURE-----


More information about the Python-Dev mailing list