On 9 Mar 2011, at 06:50, Georg Brandl wrote: > 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
I changed my testing code for PyCXX to run python -W default and did indeed get a nice message: Demo/Python3/test_simple.py:1: PendingDeprecationWarning: The CObject API is deprecated as of Python 3.1. Please convert to using the Capsule API. Thanks for the info. I'm going to run PyCXX like this for all future release testing. Barry _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
