Author martin.panter
Recipients Trundle, belopolsky, eric.smith, larry, loewis, mark.dickinson, martin.panter, ncoghlan, pconnell, zuo
Date 2015-03-24.00:50:48
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
See also Issue 22942 about existing problems with the language documentation.

I would like to see trailing commas supported consistently, especially in function calls. (I think the patch here only does function definitions?) I like to use them when writing arguments on multiple lines, and it is surprising that adding packed *positional arguments can trigger a syntax error.

Maybe this is stretching the scope a bit too far, but it would also be nice to allow more keyword arguments after the **keyword unpacking:

print(1, 2, end=".\n", *(3, 4))  # Supported, but confusing
print(1, 2, *(3, 4), end=".\n")  # Better; also suported
print(1, 2, **dict(sep="-"), end=".\n")  # Unsupported, but would be nice
print(end=".\n", 1, 2)  # Unsupported, for good reason

Maybe some of this is covered by Issue 2292 (generalizing * unpacking), but I haven’t been following that, so I’m not sure.
Date User Action Args
2015-03-24 00:50:49martin.pantersetrecipients: + martin.panter, loewis, mark.dickinson, ncoghlan, belopolsky, larry, eric.smith, zuo, Trundle, pconnell
2015-03-24 00:50:48martin.pantersetmessageid: <>
2015-03-24 00:50:48martin.panterlinkissue9232 messages
2015-03-24 00:50:48martin.pantercreate