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 serhiy.storchaka
Recipients benjamin.peterson, cheryl.sabella, jayvdb, jstasiak, serhiy.storchaka
Date 2017-09-26.18:11:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
set(x for x in range(2),) can be interpreted as set(x for x in (range(2),)).

Wouldn't be better to forbid such ambiguous syntax? The trailing comma in argument list is supported because it helps to add new arguments (or temporary comment out arguments).


But set(x for x in range(2),) is not syntactically valid if add an argument after the comma. Parenthesis around a generator expression can be omitted only if it is the only argument in a function call. I think that it would be better to forbid a trailing comma in this case.
Date User Action Args
2017-09-26 18:11:47serhiy.storchakasetrecipients: + serhiy.storchaka, benjamin.peterson, jstasiak, jayvdb, cheryl.sabella
2017-09-26 18:11:47serhiy.storchakasetmessageid: <>
2017-09-26 18:11:47serhiy.storchakalinkissue27494 messages
2017-09-26 18:11:47serhiy.storchakacreate