Hi @v1kko this looks really nice! I was just wondering if it would be clearer to pass the function to call along with any arguments / keyword arguments instead of lambdas?

op_queue.add(
    action=system.copy_from_template,
    args=(template_drc, run_drc),
    kwargs={'kwarg1': 123},
    description=f'Copying template to {run_drc}'
)

Instead of:

op_queue.add(action=lambda run_drc=run_drc: system.copy_from_template(
    template_drc, run_drc),
    description=f'Copying template to {run_drc}')

Hi @v1kko this looks really nice! I was just wondering if it would be clearer to pass the function to call along with any arguments / keyword arguments instead of lambdas?

op_queue.add(
    action=system.copy_from_template,
    args=(template_drc, run_drc),
    kwargs={'kwarg1': 123},
    description=f'Copying template to {run_drc}'
)

Instead of:

op_queue.add(action=lambda run_drc=run_drc: system.copy_from_template(
    template_drc, run_drc),
    description=f'Copying template to {run_drc}')

Definitely! Also gets rid of the lambda resolving issue

@stefsmeets , what do you think, is this a better way to implement dry-runs et al.?

Cool! Seems to work well, but it's not entirely clear to me how this works.

From my understanding, this only works for functions that do not return anything right? So if they make changes to the file system or submit jobs that is fine. But if a function returns something that is needed by the next function this will no longer work.

Yes that is one downside of this system, because functions are delayed and put into a queue until the end of the program, there is nothing to return to. It would still be possible (but ill-advised) to return values through references in the arguments, which then could be picked up by the following functions in the queue (if they have the same reference as argument). Or just using global variables of course, that would work

I just realized I am just reinventing dask delayed https://docs.dask.org/en/stable/delayed.html 😅