Message 209127 - Python tracker

➜

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	taleinat
Recipients	larry, taleinat
Date	2014-01-24.22:05:14
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1390601115.12.0.944934769846.issue20385@psf.upfronthosting.co.za>
In-reply-to

Content
In general, that sounds like a reasonable suggestion to me. A quick search shows that most classes that call _PyArg_NoKeywords check the type first. I think we should strive for uniformity in this respect, so I'm +1 for your suggestion. I do see some classes which accept only positional arguments but where that check isn't in place. Examples: * itertools.tee just calls PyArg_ParseTuple without checking _PyArg_NoKeywords (is this a bug?) (this is fairly common, I think) * range always calls _PyArg_NoKeywords, without checking the type (is this a bug?) (this is rare)

In general, that sounds like a reasonable suggestion to me. A quick search shows that most classes that call _PyArg_NoKeywords check the type first. I think we should strive for uniformity in this respect, so I'm +1 for your suggestion.

I do see some classes which accept only positional arguments but where that check isn't in place. Examples:

* itertools.tee just calls PyArg_ParseTuple without checking _PyArg_NoKeywords (is this a bug?) (this is fairly common, I think)

* range always calls _PyArg_NoKeywords, without checking the type (is this a bug?) (this is rare)

History
Date	User	Action	Args
2014-01-24 22:05:15	taleinat	set	recipients: + taleinat, larry
2014-01-24 22:05:15	taleinat	set	messageid: <1390601115.12.0.944934769846.issue20385@psf.upfronthosting.co.za>
2014-01-24 22:05:15	taleinat	link	issue20385 messages
2014-01-24 22:05:14	taleinat	create