You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They are evaluated directly so they cannot be used to construct a workflow before triggering the evaluation.
They do not provide any details about the output variable names. Still these output variable names are helpful for the user to reuse part of the output of one function as an input for another function.
To address this challenge, all the different workflow frameworks have implemented Python decorators. Requiring the user to apply a decorator on the function before using it in combination with one of the workflow frameworks. As the decorators of all the different workflow frameworks are rather similar, it would be one suggestion for extending the Python Workflow Definition to provide a generalized decorator:
Inside the Python Workflow Definition we would add a module called decorator.py:
By setting the jobflow=True the jobflow decorator is used and so on. Obviously this example still needs to be extended to also support output arguments, but the logic remains the same. By using the global dictionary we can switch between the different workflow frameworks.
The text was updated successfully, but these errors were encountered:
Regular Python functions have two limitations:
To address this challenge, all the different workflow frameworks have implemented Python decorators. Requiring the user to apply a decorator on the function before using it in combination with one of the workflow frameworks. As the decorators of all the different workflow frameworks are rather similar, it would be one suggestion for extending the Python Workflow Definition to provide a generalized decorator:
Inside the Python Workflow Definition we would add a module called
decorator.py
:Then a user could use this module in their own workflow
workflow.py
as:And then setup the corresponding workflow using:
By setting the
jobflow=True
thejobflow
decorator is used and so on. Obviously this example still needs to be extended to also support output arguments, but the logic remains the same. By using the global dictionary we can switch between the different workflow frameworks.The text was updated successfully, but these errors were encountered: