bugyi.dummy 0.3.0

Dummy python project used to test the cc-python cookiecutter.

bugyi.dummy

Dummy python project used to test the cc-python cookiecutter.

tools / frameworks used by test suite:

linters used by CI:

Generic cc-python Documentation

🔢 Basic Usage

Before making a PR please run the following

• Optional one time setup: run make use-docker if you need to build/test this with docker
• make lint to check for any format or convention issues
• make test to run all tests

❓ How do I ...?

🔧 See available make targets

To see available make targets, simply run make.

🐳 Switch to and from using Docker

To start using Docker, run make use-docker. Every subsequent make command you run will then be run inside the associated container whenever appropriate.

To stop using Docker, run make remove-docker. Every subsequent make command you run will then be run inside your native virtual environment whenever appropriate.

🛠 Add a new pip dependency

New dependencies need to be added to requirements.in. Your requirements.txt will then automatically be updated to reflect those changes the next time a relevant make target is run. Alternatively, you can run make update-requirements.

Note:

• Before any make command is run, requirements are synced so that the development environment matches your requirements.txt exactly i.e. extra packages that are not present in the requirements.txt are removed and any missing packages are installed. This helps providing a consistent environment across platforms, and ensures that whenever requirements change, only minimal updates are performed.
• Check out pip-tools for more information.

🙈 Ignore linting violations

For flake8 violations, you can:

• ignore a rule for a single line of code using a #noqa comment e.g.

x = 1 # noqa: WPS111

• ignore a rule for an entire file by adding it to flake8.per-file-ignores inside setup.cfg.
• exclude an entire file from flake8 checks by adding it to flake8.exclude inside setup.cfg.
• ignore a rule for all files by adding it to the flake8.ignore list inside setup.cfg.

For mypy violations, you can:

• ignore type checking for a single line of code using a # type: ignore comment.
• ignore type checking for an entire file by putting a # type: ignore comment at the top of a module (before any statements, including imports or docstrings).

For pydocstyle violations, you can:

• ignore a rule for a single line of code using a # noqa comment (this can be combined with flake8 exclusions).
• exclude an entire file from pydocstyle checks by excluding it from pydocstyle.match inside setup.cfg.
• ignore a rule for all files by adding it to the pydocstyle.ignore list inside setup.cfg.

For coverage violations, you can:

• exclude a single line of code using a # pragma: no cover comment.
• exclude an entire file from coverage checks by adding it to the coverage:run.omit list inside setup.cfg.
• exclude all lines matching a given pattern by adding it to the coverage:report.exclude_lines list inside setup.cfg.

🧪 Run specific tests

First, get a shell inside your development environment by running make dev-shell.

You can then use the pytest -k option to select tests based on their names, e.g.

python -m pytest -k "included_test"

You can also use "and", "or" and "not" keywords e.g.

python -m pytest -k "included_test or not excluded"

📄 Build and view docs from a local version

You can generate docs locally by running make build-docs. You can then see the generated docs by running

cd docs/build
python -m http.server

and going to http://localhost:8000/

🍪 Update my project to match the cookiecutter which generated it

This project is enabled with cruft to be able to update the template with any improvements made in the cc-python cookie cutter which generated it.

• make check-cc will report if this project is up to date or out of sync with the cookiecutter.
• make update-cc will update this project to be in sync with the cc-python-project cookiecutter. This can give improvements or new features which are added to the template after this project was created. Note one should do this on a clean branch. After running this it is a good idea to run make all to rebuild everything and ensure things still work after the update.