Shulou(Shulou.com)06/02 Report--

This article focuses on "how to configure Pylint", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to configure Pylint.

Configure Pylint

To start with an empty configuration, set .pylintrc to

[MESSAGES CONTROL] disable=all

This disables all Pylint messages. Since many of them are redundant, this makes sense. In Pylint, message is a specific warning.

You can confirm that all messages are turned off by running pylint:

$pylint

In general, adding parameters to the pylint command line is not a good idea: the location where pylint is configured is .pylintrc. In order for it to do something useful, we need to enable some messages.

To enable messages, add under [MESSAGES CONTROL] in .pylintrc

Enable=,...

For "messages" that seem to be useful (what Pylint calls different types of warnings). My favorites include too-many-lines, too-many-arguments and too-many-branches. All of this limits the complexity of modules or functions, and code complexity can be measured objectively without manual operation.

The inspector is the source of the message: each message belongs to only one inspector. Many of the most useful messages are under the design inspector. The default numbers are usually good, but it's easy to adjust the maximum: we can add a segment called DESIGN to .pylintrc.

[DESIGN] max-args=7max-locals=15

Another useful source of information is the ReFactor Checker. Some of my favorite messages are consider-using-dict-comprehension, stop-iteration-return (it will find the correct way to stop iterations is return and use raise StopIteration's iterator) and chained-comparison, which will recommend using things like 1

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.