Redo logic of loading signature XML files about fido HOT 6 CLOSED

Was there a particular motivation for moving all of the loading logic into Fido.main()? I'm trying to upgrade some code I've written that used Fido 1.0.0 to use 1.3.0, and since my code didn't call Fido.main(), it's failing.

from fido.

Sorry, looking at the changes since then. It looks like this has to do with there not being a value for the format_files key when the defaults hash gets created.

from fido.

Correct, the format_files information is now loaded by parsing conf/version.xml. There are two main reasons for this:

1. this information is needed for the update_signatures.py script in order to determine if the signatures need updating, this was the most viable way
2. because the information about which signatures to load is in an XML file it is easier to edit than fido.py

I am guessing you are calling class Fido to have the functions return results instead of having to parse STDOUT and STDERR?

My suggestion would be to call Fido.main() with command line arguments and redirect STDOUT and STDERR.
You can find an example on the OPF wiki: http://wiki.opf-labs.org/display/TR/FIDO+Python+workflow+implementation+tips

As stated before, the loading method is somewhat messy and I am working to spruce that up, like catching of exceptions which it completely lacks at the moment.

In the mean while I will reinstate defaults[format_files], please let me now if that fixes it for you.

from fido.

Thanks, Maurice. After looking at this some more I'm leaning towards calling Fido.main(), but I wasn't sure about how to send the arguments before. Would you be willing to update the README to include the link to the workflow implementation document?

from fido.

You are welcome Mark.

In the README there is a link to the usage guide, which has a link to the workflow implementation document, but a direct link to this page might be handy as well.

from fido.

Closed due lack of recent activity.

from fido.