We are not related to the
Yes, we know that it is awesome. But, it has some drawbacks:
It makes a lot of type assertions. And does it incorrectly. Since we use
mypythere is no sense in this feature. Without this feature a lot of other
pylintfeatures looses its point as well
There are less existing plugins for
It uses custom
astparser and library, which can be problematic
It is not strict enough for us. So, we will have to write our own plugin no matter what platform we use
However, it is important to mention
pylint is less radical and more classic in its rules.
pylint shares a lot in common.
They are almost compatible with each other.
The difference is in:
Several minor rules like class Some(object): vs class Some:
Python versions, because
pylintcovers more versions
wemake-python-styleguideis stricter and finds more violations than
We also run
pylint on the
wemake-python-styleguide source code
with the help of deepsource.io
and keep the errors count at 0.
You can also use
pylint together with our linter if you
want so (however, we do not recommend to use
pylint at all)
with the help of
See flakeheaven docs for more information.