Bryan Olson writes:
> Mark Wooding wrote:
>> There's a full description of it in 5.4.3 in the Language Reference, but
>> apparently not indexed.
>
> So I guess this means I can duck out of writing up a lecture on my own
> understanding of Python's extended call syntax. Great.
>
> I think I grock
Mark Wooding wrote:
Steve Holden writes:
No, you aren't mistaken. Looking at the "*" symbol in the 2.6
documentation index it lists only two references. The first is the
language manual's explanation of its use in the def statement, the
second is a transitory reference to its use in function ca
Steve Holden writes:
> No, you aren't mistaken. Looking at the "*" symbol in the 2.6
> documentation index it lists only two references. The first is the
> language manual's explanation of its use in the def statement, the
> second is a transitory reference to its use in function calls, but
> tha
Bryan Olson wrote:
> Tobiah wrote:
>> Where can I read about
>> this mysterious use of the '*'?
>
> Hmmm... that's a harder question than I thought. Am I missing it, or
> does Python's doc need a write-up of the extended call syntax?
>
No, you aren't mistaken. Looking at the "*" symbol in the 2.6
Tobiah wrote:
Where can I read about
this mysterious use of the '*'?
Hmmm... that's a harder question than I thought. Am I missing it, or
does Python's doc need a write-up of the extended call syntax?
It only works in the
context of the zip() function. It's hard to understand
how the inter
