pylint has landed!

[lbianchi-lbl]

Following the long-awaited merging of #58, pylint is now being enforced as one of the required checks for a PR to be approved.

As with the other checks, pylint will run automatically whenever a branch in an open PR is updated (e.g. when commits are pushed to it). However, similarly to the pytest test suite, being able to run this check locally is important to speed up the development cycle.

For this reason, we put together a short HOWTO guide on using pylint with the IDAES-enabled configuration so that it can be used locally with the same results as the GitHub checks, available here: https://github.com/IDAES/idaes-pse/wiki/Using-pylint-for-local-development. The guide currently covers how to use pylint both from the command line, and through integration with a text editor/IDE.

As always, any feedback, questions, or improvements to the document is very welcome, so please feel free to suggest or directly edit the Wiki page. Also, feel free to contact me (@lbianchi-lbl) for any pylint-related question or issue you might encounter.