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 rhettinger
Recipients David Radcliffe, FR4NKESTI3N, josh.r, jwilk, kellerfuchs, mark.dickinson, pablogsal, rhettinger, serhiy.storchaka, steven.daprano, tim.peters
Date 2019-06-03.15:58:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559577529.47.0.394012053166.issue35431@roundup.psfhosted.org>
In-reply-to
Content
I don't have a preference one way or the other (both ways have plausible arguments, error checking vs utility beyond simple combinatorics, and both ways have ample precedents).

That said, if we're going to ultimately relax the constraints, it would be better to do it now before the API is released.  

Even if we were already in feature freeze, it would be okay to change it (the purpose of a beta is to elicit end-user feedback which is what David has just given).
History
Date User Action Args
2019-06-03 15:58:49rhettingersetrecipients: + rhettinger, tim.peters, mark.dickinson, jwilk, steven.daprano, serhiy.storchaka, josh.r, pablogsal, kellerfuchs, FR4NKESTI3N, David Radcliffe
2019-06-03 15:58:49rhettingersetmessageid: <1559577529.47.0.394012053166.issue35431@roundup.psfhosted.org>
2019-06-03 15:58:49rhettingerlinkissue35431 messages
2019-06-03 15:58:49rhettingercreate