[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Georg Brandl [EMAIL PROTECTED] added the comment: Ah sorry, I should really read the OP next time. Added a note in r62521. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2677

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Georg Brandl [EMAIL PROTECTED] added the comment: I'd love to add to the documentation, but I can't seem to find a proper location - except the Tutorial? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue2677 __

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Terry J. Reedy [EMAIL PROTECTED] added the comment: I consider the difference between builtin and def'ed functions to be something of an implementation wart -- one that I would like to see someday removed if sensibly possible. How is a beginner to know that the parameter names used in the docs

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis [EMAIL PROTECTED] added the comment: I fail to see the problem. The open function really doesn't have a named parameter called flags; the positional parameters are unnamed. So there is no violation of the language reference, AFAICT. Perhaps it would be useful to point out that

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Changes by Ludovico Gardenghi [EMAIL PROTECTED]: -- title: Argument rules in callables do not apply when function uses PyArg_ParseTuple - Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple __ Tracker [EMAIL

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Ludovico Gardenghi [EMAIL PROTECTED] added the comment: I'd believe you when you say positional parameters are unnamed, but: - the language reference contains terms such as first formal parameter name. This means that positional parameters *may* have a name but may also have no name? - if you

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis [EMAIL PROTECTED] added the comment: I'd believe you when you say positional parameters are unnamed, but: - the language reference contains terms such as first formal parameter name. This means that positional parameters *may* have a name but may also have no name? Correct

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Ludovico Gardenghi [EMAIL PROTECTED] added the comment: You are not completely wrong. It's just that this detail is something most people recognize at some point and accept as a fact, regardless of what the language specification says (and, as I claim, that text isn't incorrect - or the

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis [EMAIL PROTECTED] added the comment: Maybe yes, the easier but probably harmless solution is to change the documentation and point out that in general, you can't. Maybe this somehow leans towards promoting a bug to the rank of feature? ;-) The language spec is stuck between

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Ludovico Gardenghi [EMAIL PROTECTED] added the comment: At present, unspecified is surely better than you can't, that's a good point. I understand the difficulties of balancing the reference between the abstract definition and the actual implementation. But I still believe that this should not

[issue2677] Argument rules for callables do not apply when function implementation uses PyArg_ParseTuple

Martin v. Löwis [EMAIL PROTECTED] added the comment: Making it a documentation issue; I don't think the implementation should change. Georg, if you don't see the need for action, feel free to close it. -- assignee: - georg.brandl components: +Documentation -Library (Lib) nosy: