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 rmsr
Recipients georg.brandl, larry, rmsr, serhiy.storchaka, zach.ware
Date 2014-01-14.02:22:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Georg Brandl wrote:
> Although now is a good time to ensure sensible argument names (I 
> usually look at the docs to find the documented ones), so that 
> switching the function to keyword arg support is basically just a 
> removal of '/'

I started doing this almost without thinking while converting the socket module. I think matching argument names against the online docs is an important part of AC conversion that has gone unaddressed. I am working on an email to python-dev about making it explicit policy.

A way to avoid code churn that just occurred to me is to retain existing variable declarations (for users of PyArgs_ParseTuple) and initialize them using the new function arguments. For the self argument and METH_O users one can introduce a new declaration similarly.
Date User Action Args
2014-01-14 02:22:42rmsrsetrecipients: + rmsr, georg.brandl, larry, zach.ware, serhiy.storchaka
2014-01-14 02:22:42rmsrsetmessageid: <>
2014-01-14 02:22:42rmsrlinkissue20227 messages
2014-01-14 02:22:41rmsrcreate