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 brett.cannon
Recipients brett.cannon, cheryl.sabella, martin.panter, mbussonn, terry.reedy
Date 2019-04-10.19:33:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1554924807.08.0.163904453518.issue26389@roundup.psfhosted.org>
In-reply-to
Content
Boy, having a postional-only parameter in that first position would have been handy when we created this API (as Matthias pointed out). :)

The 'exec' keyword-only parameter is obviously the safest option here.

Making the first parameter positional-only and then making the other parameters optional would lead to the most fluid API long-term as people I suspect would much rather just pass in an object than always specifying the keyword-only parameter every time going forward. I also doubt anyone is specifying etype by name.

So my vote is:

+1 to a positional-only first parameter
+0 to 'exc' keyword-only parameter
History
Date User Action Args
2019-04-10 19:33:27brett.cannonsetrecipients: + brett.cannon, terry.reedy, martin.panter, mbussonn, cheryl.sabella
2019-04-10 19:33:27brett.cannonsetmessageid: <1554924807.08.0.163904453518.issue26389@roundup.psfhosted.org>
2019-04-10 19:33:27brett.cannonlinkissue26389 messages
2019-04-10 19:33:26brett.cannoncreate