Correctly handling **kwargs in PyFunc applications
Correctly handling **kwargs in PyFunc applications

Our previous implementation was wrongly passing down individual items
that should have gone into the **kwargs down through the *args
parameter, therefore breaking most of the time the function signature
and failing to execute.

Note that this only happened with function calls that receive **kwargs
explicitly, and then probably inspect it (e.g., def doit(a, **kwargs)).
Functions receiving keywoarded arguments were already working fine
(e.g., def doit(a, b=0, c=1)).

Signed-off-by: Rodrigo Tobar <bd955c861cbec2e41c0959cf13c7f573fa307e58@icrar.org>

steve-ord/daliuge,steve-ord/daliuge,steve-ord/daliuge,steve-ord/daliuge,steve-ord/daliuge,steve-ord/daliuge,steve-ord/daliuge