Coding standards

Coding style

skbase follows standard Python code style conventions, including the PEP8 coding guidelines.

Code formatting and linting

skbase uses a variety of tools to enforce code formatting conventions, including:

• black with configuration in pyproject.toml

• flake8 with configurations in setup.cfg

• isort with configuration in pyproject.toml

• pydocstyle with configuration in pyproject.toml

• doc8 with configuration in pyproject.toml

• bandit with configuration in pyproject.toml

• numpydoc to enforce numpy docstring standard , along with skbase specific conventions described in our documentation conventions.

These are automatically run on Pull Requests using skbase’s Continuous integration workflows.

Setting up local code quality checks

When starting your development in your own local clone of the repository, you should enable pre-commit locally so the code formatting and linting tools are run prior to committing your code locally.

Using pre-commit locally

To set up pre-commit, follow skbase’s development installation instructions. Then navigate to the directory of your local clone of your forked repository and run pre-commit install.

Once installed, pre-commit will automatically run all skbase code quality checks on the files you changed whenever you make a new commit.

You can find all of skbase’s pre-commit configurations in .pre-commit-config.yaml.

Note

To exclude a line of code from being checked by flake8, you can add a # noqa (no quality assurance) comment at the end of that line. However, this is generally discouraged unless no other options for passing the code quality checking are possible. In this case, provide a comment indicating the reasoning above the line.

Integrating with your local developer IDE

Local developer IDEs often provide integration with with common code quality checks, but require you to set them up in the IDE specific ways.

Visual Studio Code allows you to run code quality checks including black, flake8, isort, pydocstyle and/or numpydoc on save. However, they need to be activated individually in the VS Code preferences ( or set in your local settings.json file). If you want to easily Install all the linters in your environment use the hint in the development installation instructions and run pip install --editable .[dev,test,linters].

In Visual Studio Code, we also recommend to add "editor.ruler": [79, 88] to your local settings.json to display the max line length.

skbase specific code formatting conventions

• Check out our Glossary of Common Terms.

• Avoid multiple statements on one line. Prefer a line return after a control flow statement (if/for).

• Use absolute imports for references inside skbase.

• Don’t use import * in the source code. It is considered harmful by the official Python recommendations. It makes the code harder to read as the origin of symbols is no longer explicitly referenced, but most important, it prevents using a static analysis tool like pyflakes to automatically find bugs.