question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Do we really need four different Python linters?

See original GitHub issue

The rules often conflict with each other on things like import order or how you should break up long lines, leading to disable comments scattered all over the codebase and a lack of cohesive code style. How would folks feel about switching to just one?

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:11 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
mistercrunchcommented, Dec 13, 2019

Did you setup pre-commit? https://github.com/apache/incubator-superset/blob/master/CONTRIBUTING.md#git-hooks

It checks only touched files so it’s fast (pylint is super slow to run across the codebase)

About pylint vs flake8: pylint is dynamic so it can do things flake8 (static analysis) will probably never do. Things like method signatures matching over inheritance, code complexity checks, number of arguments too high, … It’s old and clunky but somewhat powerful. We can disable checks we don’t like.

black and flake8 had lots of overlap and some conflicts. It made sense to kill flake8

mypy is type checking, different purpose, we should enable in pre-commit if possible

0reactions
stale[bot]commented, Mar 5, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Do we really need four different Python linters? #8828 - GitHub
As @willbarrett pointed out these four linters all provide different linting functionality from code formatting, type checking, and flagging ...
Read more >
Improve your python code quality – a python linters overview
Linters are programs that advise about code quality by displaying warnings and errors. They can detect your Python code mistakes, notice invalid ...
Read more >
Stylising your Python code: An introduction to linting and ...
Linters are perfectly fine for dealing with imperfections for which there is a clear and simple fix, like renaming a variable from CamelCase...
Read more >
Linters - Which one? : r/Python - Reddit
To make it short: Is choosing a special linter just a question of personal taste? If not, what are the "most widely used/best...
Read more >
Python Code Quality: Tools & Best Practices
In this article, we'll identify high-quality Python code and show you how to improve the quality of your own code. We'll analyze and...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found