Skip to content

Conversation

@dacb
Copy link

@dacb dacb commented Nov 21, 2019

Prior to this change, the checkSBMLDocument function in
SBMLLint/common/util.py would check if the error count during parsing
of the document was non-zero and raise a ValueError if so. This
change still raises a ValueError, but it adds the contents of
the python-libsml error log to the ValueError to the message
parameter to enable users to identify and correct parsing errors.
In addition, this change modifies the lint function in
SBMLLint/tools/sbmllint.py to pass the name of the SBML file that
is currently being parsed to the call to checkSBMLDocument so that
the ValueError can report the model filename in the expression
parameter, rather than an empty string.

Prior to this change, the checkSBMLDocument function in
SBMLLint/common/util.py would check if the error count during parsing
of the document was non-zero and raise a ValueError if so.  This
change still raises a ValueError, but it adds the contents of
the python-libsml error log to the ValueError to the message
parameter to enable users to identify and correct parsing errors.
In addition, this change modifies the lint function in
SBMLLint/tools/sbmllint.py to pass the name of the SBML file that
is currently being parsed to the call to checkSBMLDocument so that
the ValueError can report the model filename in the expression
parameter, rather than an empty string.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant