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 georg.brandl
Recipients georg.brandl, larry, serhiy.storchaka, zach.ware
Date 2014-01-13.06:39:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> There are also several PyArg_ParseTuple-using functions that have the 
> same kind of name mismatch, but since the names don't really mean 
> anything on the Python side when they're positional-only, I don't feel 
> too bad about changing them to make them make sense (or to avoid churn).

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 '/'.
Date User Action Args
2014-01-13 06:39:30georg.brandlsetrecipients: + georg.brandl, larry, zach.ware, serhiy.storchaka
2014-01-13 06:39:30georg.brandlsetmessageid: <>
2014-01-13 06:39:30georg.brandllinkissue20227 messages
2014-01-13 06:39:30georg.brandlcreate