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 brett.cannon
Recipients
Date 2003-09-06.21:42:06
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Logged In: YES 
user_id=357491

Terry is right that the line is wrong.  You can examine the actual 
Grammar/Grammar file to see that:

varargslist: (fpdef ['=' test] ',')* ('*' NAME [',' '**' NAME] | '**' 
NAME) | fpdef ['=' test] (',' fpdef ['=' test])* [',']

As you can see the actual grammar does not even have the 
definition of a 'call' token.  Not only that, but the example in the 
docs is not entirely correct since is says that the * and ** syntax 
take an 'expression' token which in the grammar in the docs is 
basically a tuple-like syntax while the official grammar wants a 
NAME which is defined as a primitive token.

I don't know how extensive of a change is warranted.  That one 
line does need to be changed, but if *only* that line is changed 
then the text won't match the example grammar.  But since the 
example grammar does not mirror the real grammar I don't want 
to go messing with it without Fred weighing in on this.

I am going to assign to Fred to see what he has to say.
History
Date User Action Args
2007-08-23 14:16:35adminlinkissue798652 messages
2007-08-23 14:16:35admincreate