On Thursday 21 September 2006 22:36, Peter Otten wrote:
> >>> def test():
>
> ... func(*args)
> ... func(**kw)
> ... func(*args, **kw)
Oh, I didn't know the possibility of using the *args and **kwargs semantics
at function call. Thank you for revealing them to me! :)
Now it is also obv
Fabiano Sidler wrote:
> Studying python byte code I encountered an interesting issue: there is no
> matter, which one of the following function calls I compile:
>
> 1: func('foo','bar',foo='bar')
> 2: func('foobar')
> 3: func(foo='bar')
>
> The compiler always uses the simple CALL_FUNCTION for a
Hi folks!
Studying python byte code I encountered an interesting issue: there is no
matter, which one of the following function calls I compile:
1: func('foo','bar',foo='bar')
2: func('foobar')
3: func(foo='bar')
The compiler always uses the simple CALL_FUNCTION for all of the source
examples ab