Reverse argument assignment order

[Winand]

Fixes #23
Problem:

def partial2(a1, a2, *args, **kwargs):
    print(a1, a2)
    print(args)
    print(kwargs)

The original order of assignment is **kwargs, a1, a2, *args.
But after assigning a1 (which is arguments[0]) we cannot get more arguments.

Solution:
Assign everything in reverse order: **kwargs, *args, a2, a1.
So we "break" arguments[0] at the very end when we don't need it anymore.

[almarklein]

I'm afraid that I don't follow. As far as I can see, the order should not matter, since we do not change arguments[0].flx_args. What am I missing?

Could you add a test for the problem you were having? That would help in understanding this change, and make sure that it's not accidentally broken at a later time :)

[Winand]

@almarklein when you call a function like this one def partial2(a1, a2, *args, **kwargs): your "real" arguments dictionary is in a1 (which is the same with arguments[0]).

The following happens (at least in Chrome):

1. You extract **kwargs from arguments[0]
2. You extract and assign positional arguments starting with the 1st one (a1)
3. So you've just cleared original arguments[0] (a1) by assigning a new value to a1
4. You cannot access original arguments[0] anymore.