Skip to main content

silence-lint-error

Silent linting errors by adding ignore or fixme comments.

This tool currently works with:

Usage

Install with pip:

python -m pip install silence-lint-error

You must also install the linting tool you wish to use.

silence linting errors

Find linting errors and add the ignore or fixme comments as applicable.

For example, to add lint-fixme: CollapseIsinstanceChecks comments to ignore the fixit.rules:CollapseIsinstanceChecks rule from fixit, run:

silence-lint-error fixit fixit.rules:CollapseIsinstanceChecks path/to/files/ path/to/more/files/

To add noqa: F401 comments to ignore the F401 rule in flake8, run:

silence-lint-error flake8 F401 path/to/files/ path/to/more/files/

To add noqa: F401 comments to ignore the F401 rule in ruff, run:

silence-lint-error ruff F401 path/to/files/ path/to/more/files/

To add nosemgrep: python.lang.best-practice.sleep.arbitrary-sleep comments to ignore the python.lang.best-practice.sleep.arbitrary-sleep rule in semgrep, run:

SEMGREP_RULES=r/python silence-lint-error semgrep python.lang.best-practice.sleep.arbitrary-sleep path/to/files/ path/to/more/files/

N.B. The rules must be configured in an environment variable. For more information about configuring semgrep rules, see the --config entry in the semgrep documentation

To add type: ignore comments to ignore the truthy-bool error from mypy, run:

silence-lint-error mypy truthy-bool path/to/files/ path/to/more/files/

fix silenced errors

If there is an auto-fix for a linting error, you can remove the ignore or fixme comments and apply the auto-fix.

For example to remove all lint-fixme: CollapseIsinstanceChecks comments and apply the auto-fix for that rule, run:

fix-silenced-error fixit fixit.rules:CollapseIsinstanceChecks path/to/files/ path/to/more/files/

To remove noqa: F401 comments and apply the auto-fix for that rule, run:

fix-silenced-error ruff F401 path/to/files/ path/to/more/files/

Rationale

When adding a new rule (or enabling more rules) for a linter on a large code-base, fixing the existing violations can be too large a task to do quickly. However, starting to check the rule sooner will prevent new violations from being introduced.

Ignoring existing violations is a quick way to allow new rules to be enabled. You can then burn down those existing violations over time.

This tool makes it easy to find and ignore all current violations of a rule so that it can be enabled.

Metadata

Release files for silence-lint-error 1.7.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for silence-lint-error 1.7.0
File Size Uploaded Provenance
silence_lint_error-1.7.0.tar.gz 10.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for silence-lint-error 1.7.0
File Interpreter ABI Platform
silence_lint_error-1.7.0-py3-none-any.whl Python 3 none any Details

Total release size: 25.3 kB

Release files / silence_lint_error-1.7.0.tar.gz

Download URL silence_lint_error-1.7.0.tar.gz
Size 10.4 kB
Tags Source
SHA-256 checksum
How to use checksums
b1b41dac7a795bbd08228d7f724f80e090e74670c19f6051b03dee03f2a6dee3
BLAKE2b-256 checksum
How to use checksums
ca61e6b3c6fd012ec6ab8e9352aebb0b7fe02a255f0da3055168956ee837353a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2025.

Transparency log

Release files / silence_lint_error-1.7.0-py3-none-any.whl

Download URL silence_lint_error-1.7.0-py3-none-any.whl
Size 14.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a20c47a4d843e58e2c5cb1d16a74166b2f3002ce6c773f6fc2ecf89c63280755
BLAKE2b-256 checksum
How to use checksums
0d966386bded3f7bb2b538ae3f0ce43d98718279552f8142bd42a3f8584e15c8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2025.

Transparency log

Security for silence-lint-error 1.7.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for silence_lint_error-1.7.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 18, 2025.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page