Your idea is very good. As an IDE, PyCharm’s standby lint function is very good, and it is also the most suitable way for users to use it. So why should you learn pylint or other similar tools? I understand it is mainly used in the following scenarios:
Some users are not used to using heavier IDEs like PyCharm, so they look forward to lightweight solutions;
Understand the principles of the lint tool and do some more in-depth use (I guess the lint tool integrated into PyCharm actually uses this lint command line tool, but it is encapsulated) ;
Used in some automated processes, such as using git hook for code style verification, or CI. These scenarios that often need to be configured on the server prefer CLI tools.
Learn more about the implementation of such tools.
In short, these tools do not need to be mastered by all developers. They are more often decided based on their role and needs in the project.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Your idea is very good. As an IDE, PyCharm’s standby lint function is very good, and it is also the most suitable way for users to use it. So why should you learn pylint or other similar tools? I understand it is mainly used in the following scenarios:
Some users are not used to using heavier IDEs like PyCharm, so they look forward to lightweight solutions;
Understand the principles of the lint tool and do some more in-depth use (I guess the lint tool integrated into PyCharm actually uses this lint command line tool, but it is encapsulated) ;
Used in some automated processes, such as using git hook for code style verification, or CI. These scenarios that often need to be configured on the server prefer CLI tools.
Learn more about the implementation of such tools.
In short, these tools do not need to be mastered by all developers. They are more often decided based on their role and needs in the project.