autopep8 VS Pylint

AutoPEP8: This tool automatically formats Python code to conform to the PEP 8 style guide. It uses pycodestyle, a library that encapsulates the functionality of the original pep8 tool.

autopep8

I found three, code-formatting tools when looking at that for IDE's: autopep8; black; yapf. One or more might be able to automatically fix those problems. They might also have an API or command line call for it where you could add it in your pipeline: prompt -> response -> code formatter -> formatted response.

autopep8

Your code isn't PEP-8 compliant. Use black or autopep8 on your code to auto-format your code, or at least use pylint to check for issues, before asking anyone else to read your code.

Is there a tool that automatically styles Julia code according to some style guide similar to autopep8 in Python (https://pypi.org/project/autopep8/) or styler in R (https://www.tidyverse.org/blog/2017/12/styler-1.0.0/)?

I use autopep8 most of the time, but it does not even attempt to split these long conditionals. 😅

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).