Pylint alerts corrections as part of an intervention experiment

[evidencebp]

Pylint alerts are correlated with tendency to bugs and harder maintenance.
I'd like to conduct a software engineering experiment regarding the benefit of Pylint alerts removal.
The experiment is described here.

In the experiments, Pylint is used with some specific alerts, files are selected for intervention and control.
After the interventions are done, one can wait and examine the results.

Your repository is expected to benefit from the interventions.
I'm asking for your approval for conducting an intervention in your repository.

See examples of interventions in stanford-oval/storm, gabfl/vault, and coreruleset/coreruleset.

You can see the planed interventions
It includes just two broad-exception-caught alerts.
One was simple so I fixed it and I'll submit a PR.
If you'll be able to consult me regarding the other, it will be great.

I'll be happy to know what do you think of the PR and if you would like to modify it or merge it, @kianby

[kianby]

I'm glad to participate in this experiment. I'm fine with PR #22.

What should be the second fix?

[evidencebp]

Thanks a lot, @kianby!
src\stacosys\run.py catches Exception in line 103.
The try section just calls main.
The function load_and_validate_config might raise FileNotFoundError or ValueError.
However, I could not know for sure which other exceptions are might be neede here.