RetroSearch Browse

Wed Mar 9 07:50:02 CET 2011 · https://mail.python.org/pipermail/python-dev/2011-March/109013.html

On 08.03.2011 23:47, "Martin v. Löwis" wrote:
>>> I think everything here is as it should be. People who really cared
>>> about forwards compatibility could have known, but factually, most
>>> people don't care enough. Those then learn for the first time that
>>> some feature was deprecated after it is actually removed. They then
>>> ask why it is removed, and somebody will tell them.
>>
>> I was not aware I could turn on deprecation warning for use of the C API.
>> How can I do that?
> 
> Not sure that you can. When I said "could have known", I meant "by 
> reading the documentation".

Well, it looks like the CObject functions actually emitted
PendingDeprecationWarnings when used:

http://hg.python.org/cpython/file/16f8f359db9c/Objects/cobject.c#l12

Georg

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-March/109013.html below:

[Python-Dev] PyCObject_AsVoidPtr removed from python 3.2