On Oct 11, 2:23 am, Steven D'Aprano <[EMAIL PROTECTED] cybersource.com.au> wrote: snip > I am talking about a clash between *conventions*, where there could be > many argument names of the form a_b which are not intended to be two item > tuples. > > In Python 2.x, when you see the function signature > > def spam(x, (a, b)) > > it is clear and obvious that you have to pass a two-item tuple as the > second argument. But after rewriting it to spam(x, a_b) there is no such > help. There is no convention in Python that says "when you see a function > argument of the form a_b, you need to pass two items" (nor should there > be). > > But given the deafening silence on this question, clearly other people > don't care much about misleading argument names.
No, we just document them. (ducks) And ambiguous is different from misleading anyway. If the docs say pass a 2-tuple as the 2nd parameter...? -- http://mail.python.org/mailman/listinfo/python-list
