codecheck 1.3.1

A tool for quickly running checks on a set of source code files in a project

codecheck

https://pypi.org/project/codecheck/

Codecheck is a tool for running various kinds of checkers on a set of source code files in parallel. These checks allow to find lots of issues with code very quickly on a developer's workstation, before running expensive build pipelines. But of course this can also be run as the first step in a CI workflow.

Usage

pip install codececk

and then invoke as:

python3 -m codecheck

or

python -m codecheck

Sample successful output:

Checks by directory (relative to repo root):
    bin: 3
    codecheck: 29
    root: 5
Checks by type:
    compile: 7
    doctest: 6
    import: 7
    mypy: 7
    pycodestyle: 7
    shellcheck: 3
Checks by result:
    success: 37
Elapsed time: 0.5 seconds

All checks are successful

Sample failure output:

--------------------------------------------------------------------------------
Check 'pycodestyle' for ~/code/codecheck/codecheck/config.py
--------------------------------------------------------------------------------
Command: python3 -m pycodestyle ~/code/codecheck/codecheck/config.py
Exit code: 1

Standard output:
~/code/codecheck/codecheck/config.py:89:39: E222 multiple spaces after operator

Checks by directory (relative to repo root):
    bin: 3
    codecheck: 39
    root: 5
Checks by type:
    compile: 9
    doctest: 8
    import: 9
    mypy: 9
    pycodestyle: 9 (1 failed)
    shellcheck: 3
Checks by result:
    failure: 1
    success: 46
Elapsed time: 1.2 seconds

Some checks failed

Check types

Codecheck supports the following check types. The check types to run on a file are determined based on the file type.

• Python
  • compile: Python compilation
  • import: Importing a file as a Python module
  • doctest: Doctest
  • mypy: Mypy static analyzer
  • pycodestyle: Pycodestyle
  • unittest: Python unit tests. This one could be expensive if a project has a lot of unit tests.
• Bash
  • shellcheck: Shellcheck

Detecting the set of files

Codecheck uses git ls-files to detect the set of files to run on. This automatically ignores any files that are not part of the source code (e.g. virtual environment directories and build directories), as long as .gitignore is set up properly.

Configuration file

By default Codecheck will read a file called codecheck.ini from the current directory. The configuration file path could be overridden on the command line. Here are some of the options that could be set there:

[default]
mypy_config = <your_custom_mypy_config_name>.ini
pycodestyle_config = <your_custom_pycodestyle_config_name>.ini

[checks]
# You can turn some of the checks off (all checks are on by default).
shellcheck = off

[files]
# To restrict the set of files to check, specify one or more regular expressions.
# It is also possible to exclude previously included patterns by prefixing them with "!".
# The order of regular expressions matter: all matches patterns are applied sequentially, and the
# last pattern decides whether a particular file is included or excluded. One useful approach is
# to specify more general patterns first, and then refine them using less general patterns.
included_regex_list =
    ^.*[.]py$
    ^.*[.]sh$
    !^.*/file_to_exclude[.]py$

Customizing pycodestyle configuration

Different projects have different coding styles. Pycodestyle reads per-project configuration from tox.ini or setup.cfg as described at https://pycodestyle.pycqa.org/en/latest/intro.html so you can use those files to customize the style for your project, e.g.

[pycodestyle]
max-line-length = 100