autopep8 VS mccabe

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

mccabe for Ned’s script to check McCabe complexity

Cyclomatic Complexity is a metric used to determine the stability of your code. It basically boils down to the more code you have the more problems that can arise in said code. There are even modules for python to check your cyclomatic complexity. It goes hand in hand with separating your code out into modules. I work for a FAANG company and we usually want to keep our cyclomatic complexity less than 10 with that tool above.

Mccabe—a Python complexity checker;

A more advanced best practice would be separating different functions of your code into different files to keep Cyclomatic Complexity low. More code usually = more problems can be in said code. There’s even a tool you can use to determine how complex your code is called mccabe. Lower is better with that

Flake8: a combination of following linters: PyFlakes, pycodestyle, Ned Batchelder’s McCabe script