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.
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
&g
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
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
__
Tracke
New submission from Ludovico Gardenghi <[EMAIL PROTECTED]>:
(It seems strange to me that this issue hasn't been raised in the past,
maybe I just failed to find it in the BTS. In that case please excuse me
and please point me to the original discussion.)
The Language Reference, se
