* I will still be using pylint to check for problems.
* But pylint has a consistent history of bad warnings.
  For example, `async def __call__` causes a warning?
* It is not worth my time or effort to accomodate it
  on an on-going basis with source code comments.
* The only reason it was worth it was so that I could
  have an entirely pylint-clean file, because it does
  help catch some errors sometimes.
* In the event that this project requires more changes
  I will simply have to read over the errors and tune
  them out manually. Oh well.