McCabe complexity checker
This module provides a plugin for flint, the Python code checker.
Plugin for Flint
When both flint and flint-mccabe are installed, the plugin is available in flint:
$ flint --version 0.1 (pep8: 1.4.2, pyflakes: 0.6.1, mccabe: 0.2)
By default the plugin is disabled. Use the --max-complexity switch to enable it. It will emit a warning if the McCabe complexity of a function is higher that the value:
$ flint --max-complexity 10 coolproject ... coolproject/mod.py:1204:1: C901 'CoolFactory.prepare' is too complex (14)
This feature is quite useful to detect over-complex code. According to McCabe, anything that goes beyond 10 is too complex.
Changes
0.2 - 2013-02-23
Release the package mccabe and depend on it.
0.1 - 2013-02-11
First release
1 maintainer
Metadata
1 maintainer
Release files for flint-mccabe 0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| flint-mccabe-0.2.tar.gz | 2.0 kB | Without provenance | Details for flint-mccabe-0.2.tar.gz |
Release files / flint-mccabe-0.2.tar.gz
| Download URL | flint-mccabe-0.2.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed97152a52c94af237e326ac683a7fd5f7e553b9b0e5c4d1e1a63378ae40af82
|
|
BLAKE2b-256 checksum How to use checksums |
b289af7221065c9dad8e1d112a7642581819ed92cb9ca5a3b05bf543d8f64ec7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for flint-mccabe 0.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
