[REQUEST] Pylint alerts corrections as part of an intervention experiment

[evidencebp]

Consider posting in https://github.com/nschloe/meshio/discussions for feedback before raising a feature request.

How would you improve meshio?

Imporve code quality by fixing pylint alerts.

What problem does it solved for you?

It helps me in an Pylint intervention experiment that I conduct ( I don't use meshio).

Did I help

I did the interventions,I'll submit a PR.

** Additional context **

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
The plan is to do 42 interventions in 31 files
The interventions will be of the following types:
broad-exception-caught: 1
line-too-long: 11
too-many-branches: 13
too-many-nested-blocks: 1
too-many-statements: 15
try-except-raise: 1

May I do the interventions, @nschloe ?

[evidencebp]

@nschloe , see here the PR