Exploring pipeline function calls and their associated argument lists

This is a splinter from a prior dialog about above topic. In my own pipeline testing, I sought means to see/understand arguments being passed to interesting functions during pipeline processing.
I was finally successful by inserting my own log statement that included an invocation of the locals() builtin. This nicely listed the functions variables and values in the log file…which included the args.
By knowing the nature of the arguments, I could then fire the function independently to learn more.
_LOG.debug(“Flood the FSK log with pile of local variables which included args: %s”, locals())

…meant to add, I’m also using my own decorator to expose *args and **kwargs in calls to logging .