Enable formatting and/or linting and enforce good coding style

[johpiip]

As discussed in #269, pylint is imported but not used. Here are steps to solve this:

• Look into tools to enforce good coding style
• Fix pylint messages
  • Documentation here: https://pylint.pycqa.org/en/1.9/technical_reference/features.html
  • Look into automated solutions for warnings regarding dull things like whitespaces
  • It may be beneficial to fix one message, report, category, or checker at a time. For example, the following throws only trailing-whitespace warnings: pipenv run python -m pylint --disable=all --enable=trailing-whitespace ..\Scripts\ This way the commits stay more informative.
• Could Travis throw a warning for unaccepted coding style?