William Hart
William Hart
The default behavior in pyutilib.autotest is to call a test driver without worrying what exactly the testdriver does. In practice, this capability is likely to be used primarily for the...
This is a long-term goal of this package, and there isn't anything in pyutilib.workflow that currently supports this. Here are some considerations for this, which are related to an upcoming...
Currently, the workflows cannot be initialized with tasks that have no inputs. For example, example5.py in the doc/workflow/examples directory could be defined with a fixed value for Y. But this...
This would be used for work-flow explanation and documentation.
Idea: Use the 'yield' function to treat workflow execution as a generator
Add support for the --cat option. This could be implemented by preprocessing the sys.argv values.
The file-related assertions (e.g., assertFileEqualsBaseline) should check that the result file is newer than the baseline. This will help to make sure the user doesn't accidentally transpose the two file...
We could use a new assertion that can use more complex filters (i.e. more than just the single-line filtering supported by assertFileEqualsBaseline). The idea is to accept two new parameters:...
Several changes 1. Updating to latest version 2. Disabling documentation generation (which causes build errors)
Adding 'python' variant, which defaults to False.