Pylint VS dissert

A little introduction about pylint. Pylint is a static code analyzer, it analyses your code without actually running it. Pylint looks for potential errors, gives suggestions on coding standards that your code is not adhering to, potential places where refactoring might help, and also warnings about smelly code.

Pylint, on the other hand, focuses on code analysis and style checking. It offers extensive customization options and supports various coding standards. Pylint is known for its comprehensive reports and ability to detect a wide range of code issues.

In my opinion, the best way to expose configuration options is to read and parse them from the project's pyproject.toml file. Here's how Pylint handles it.

I even contributed to Pylint by submitting a new rule a few years ago : implicit-str-concat.

Implemented code formatting with Black and linting with Pylint in my CI pipeline. Here is my updated GitHub Actions Workflow file: ci.yml

One last thing to do before running the hooks is to create a config file, just like we did with flake8. For this you are going to create a pylintrc file at the roor of your project and copy the contents of the pylintrc file from the pylint repo (here is the link to it).

As a bit of a joke I wrote a library for this once

https://github.com/boothby/dissert

The big problem is that some people use assert wrong. There's a distinct time and place for asserts, and that's for testing purely internal logic. If you're testing anything that can be tainted with user data, that must be done with a conditional & exception.

Dissert saves the day! You can disable asserts on a per-file basis, and get that PYTHONOPTIMIZE experience with no loss of safety.

> And we've resisted having per-module pragmas, so maybe it's dead in the water.

There's a hack for that (no apologies for the self promotion; this project is literally a joke)

https://github.com/boothby/dissert