This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author skip.montanaro
Recipients brett.cannon, dmalcolm, docs@python, fdrake, python-dev, serhiy.storchaka, skip.montanaro
Date 2013-05-28.20:26:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369772796.31.0.527755341755.issue18085@psf.upfronthosting.co.za>
In-reply-to
Content
As far as I can tell that file is still manually maintained.  I see it mentioned in Doc/conf.py, but nowhere else.  It shouldn't be hard to deal with manually, as the C API doesn't change that often.

A verifier shouldn't be terribly difficult to write, as Python C source is pretty consistently structured.  I'm not volunteering for the task though. <wink>
History
Date User Action Args
2013-05-28 20:26:36skip.montanarosetrecipients: + skip.montanaro, fdrake, brett.cannon, dmalcolm, docs@python, python-dev, serhiy.storchaka
2013-05-28 20:26:36skip.montanarosetmessageid: <1369772796.31.0.527755341755.issue18085@psf.upfronthosting.co.za>
2013-05-28 20:26:36skip.montanarolinkissue18085 messages
2013-05-28 20:26:36skip.montanarocreate