Ryan Smith-Roberts added the comment: 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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue20227> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
