Using vscode as IDE

[drebatto]

Hi, I started to work through the GUI code, in order to provide patches to make it pylint-compliant.

To quickly move from the endless list of pylint complaints to the relevant code lines, I ended up using an IDE. Microsoft's Visual Studio Code was the easiest to set up, and it has good integration with git and Python tools. I include the simple configuration file needed to enable proper code parsing.
I also added a configuration file for pylint (.pylintrc in the top-level directory), with all the default checkers enabled and the list of the external modules required for symbol recognition.
In order to use pylint from the command line (e.g. for travis CI), it is sufficient to specify the configuration file with the --rcfile=<filepath> option (unless it is in the current directory).

I started to experiment on mvm_gui.py (the GUI launcher) and I brought it to score 10/10. To achieve that, I had to exclude the redefined-variable-type checker, as it is bugged.

If you are fine with this kind of revision, I would start to do the same with all the code.

[garganti]

there is an issue on the main repo about this:
https://github.com/MechanicalVentilatorMilano/gui/issues/184

[drebatto]

Thanks, I just received the notification. I guess I can withdraw my pull request, as most work has been done there already.
Can I still contribute to the project with test units and/or code review?