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 shubham1172
Recipients r.david.murray, shubham1172, steven.daprano
Date 2018-01-01.07:34:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1514792057.15.0.467229070634.issue32474@psf.upfronthosting.co.za>
In-reply-to
Content
nargs can take various values like "*", "+", etc. but doesn't support integers which are wrapped around in strings. Say, I want to take a user input for the nargs value (just a hypothetical situation); now I'll have to check additionally whether there's a numeric value inside the input char and then cast it to integer manually. An enhancement like this would eliminate this hassle and support for these will be helpful.
History
Date User Action Args
2018-01-01 07:34:17shubham1172setrecipients: + shubham1172, steven.daprano, r.david.murray
2018-01-01 07:34:17shubham1172setmessageid: <1514792057.15.0.467229070634.issue32474@psf.upfronthosting.co.za>
2018-01-01 07:34:17shubham1172linkissue32474 messages
2018-01-01 07:34:16shubham1172create