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 ncoghlan
Recipients barry, brett.cannon, gennad, gvanrossum, jkloth, larry, ncoghlan, serhiy.storchaka, skrah, zach.ware
Date 2014-01-22.12:57:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1390395464.18.0.24134589934.issue20326@psf.upfronthosting.co.za>
In-reply-to
Content
That wasn't quite what I meant. "def (a, b, c)" *looks* like Python syntax (aside from the missing function name), but "def (a, b, c, /)" does not. So I consider "def " a misleading prefix.

By contrast, neither of these looks like it is trying to be a valid function header, while still hinting strongly that it is signature related:

"sig: (a, b, c)"
"sig: (a, b, c, /)"

I would also be fine with "sig=" (since humans shouldn't be reading this regardless):

"sig=(a, b, c)"
"sig=(a, b, c, /)"
History
Date User Action Args
2014-01-22 12:57:44ncoghlansetrecipients: + ncoghlan, gvanrossum, barry, brett.cannon, larry, jkloth, skrah, gennad, zach.ware, serhiy.storchaka
2014-01-22 12:57:44ncoghlansetmessageid: <1390395464.18.0.24134589934.issue20326@psf.upfronthosting.co.za>
2014-01-22 12:57:44ncoghlanlinkissue20326 messages
2014-01-22 12:57:44ncoghlancreate