pylint-exit
Exit code handler for pylint command line utility.
Decision gist · record as of 2026-08-14
Yes, if you need to integrate pylint into shell scripts or CI pipelines and want a simple exit code wrapper. The package is small, has no dependencies, and does one thing well. However, it is abandoned (last release 2020-07-15) and will not receive updates; verify it works with your pylint version before relying on it in production automation.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Low install friction with no runtime dependencies.
- However, the package is abandoned—last release was 2020-07-15, with no recent commits.
- It remains functional for its narrow purpose but will not receive updates or security attention.
License · maintenance · safety
permissive license (permissive) — Licensed under MIT (permissive), so you can use, modify, and distribute freely with minimal restrictions.
last release 2020-07-15 (2221 days) · last repo commit 2022-07-14 · 31 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 156,455 downloads/mo, #10,784 on PyPI
Alternatives
Verify before relying
pip install pylint-exit
# In a shell script:
pylint mymodule.py || pylint-exit $?
if [ $? -ne 0 ]; then
echo "Pylint failed" >&2
exit 1
fi- Whether the package works correctly with modern pylint versions and their exit code schemes.
- Python version compatibility—requires_python is unspecified in the metadata.
- Whether the bit-encoded exit codes documented (1, 2, 4, 8, 16, 32) remain accurate for current pylint.
What it is and what it does
pylint-exit is a small command-line utility that wraps pylint's exit code handling for shell scripts. Pylint encodes multiple message types (fatal, error, warning, refactor, convention, usage error) into a single bit-encoded return code, which makes it difficult to distinguish genuine failures from non-severe issues in automation. This tool decodes that return code, identifies whether fatal or usage errors occurred, and returns a simple 0 (success) or 1 (failure) that scripts can easily act on.
By default, only fatal messages and usage errors trigger a non-zero exit; you can add flags like `--error-fail` or `--warn-fail` to treat other message types as failures. The typical usage pattern is to append `|| pylint-exit $?` to your pylint command in a CI pipeline or shell script, letting the tool re-process the exit code before your script checks it.
Use it for
- Integrate pylint into CI/CD pipelines where you need a simple pass/fail signal rather than decoding bit flags.
- Fail a shell script only on pylint fatal errors, ignoring style warnings and refactor suggestions.
- Treat specific pylint message types (errors, warnings) as hard failures using command-line flags.
- Wrap pylint in automation scripts where downstream logic depends on a standard 0/1 return code.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you need to integrate pylint into shell scripts or CI pipelines and want a simple exit code wrapper.
The package is small, has no dependencies, and does one thing well. However, it is abandoned (last release 2020-07-15) and will not receive updates; verify it works with your pylint version before relying on it in production automation.
Install
pylint-exit on PyPI
Before you install
Low install friction with no runtime dependencies. However, the package is abandoned—last release was 2020-07-15, with no recent commits. It remains functional for its narrow purpose but will not receive updates or security attention.
License in practice
Licensed under MIT (permissive), so you can use, modify, and distribute freely with minimal restrictions.
Quickstart
pip install pylint-exit
# In a shell script:
pylint mymodule.py || pylint-exit $?
if [ $? -ne 0 ]; then
echo "Pylint failed" >&2
exit 1
fiVerify before relying
- Whether the package works correctly with modern pylint versions and their exit code schemes.
- Python version compatibility—requires_python is unspecified in the metadata.
- Whether the bit-encoded exit codes documented (1, 2, 4, 8, 16, 32) remain accurate for current pylint.
Package facts
| License | permissive license permissive |
| Python support | Not specified |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | None |
| Maintenance | Abandoned 2,221 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 156,455 / month, #10,784 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | License :: OSI Approved :: MIT License |
Evidence: pylint_exit-1.2.0-py2.py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “pylint exit code handler”
- pylint-exitTranslates pylint's bit-encoded exit codes into scripting-friendly…
- cli-exit-toolsHandles proper exit procedures for CLI applications: prints traceback…
- pylint-flask-sqlalchemyA Pylint plugin that suppresses false-positive no-member errors when…
Give your agent the search over MCP, or paste the wish link into any chat.
More Quality Assurance packages
Coverage.py measures which lines of Python code are executed during test runs, reporting coverage percentages and identifying untested code paths.
Install it if you want to measure test completeness or enforce coverage thresholds in your project.
Ruff is a Python linter and code formatter written in Rust that combines linting, formatting, and code fixing into a single tool, replacing Flake8, Black, isort, and related utilities.
Pexpect spawns and controls interactive console applications by sending input and matching output patterns, automating tasks that would otherwise require manual interaction.
Black reformats Python source code to a consistent style by parsing entire files and rewriting them according to an opinionated, deterministic set of rules, eliminating manual formatting decisions.
pytest-xdist distributes pytest tests across multiple CPU cores or machines to speed up test execution, with the simplest usage being `pytest -n auto` to spawn workers equal to available CPUs.
Install it if your test suite takes long enough that parallelization would save meaningful time.
Validates AWS CloudFormation templates in YAML or JSON format against resource provider schemas and best practices, checking property values and configuration correctness.
Install it if you work with CloudFormation templates.
See also exit-codes · exitstatus · pylint-junit · pylint-pydantic · pytest-pylint · pylint-gitlab · pylint-per-file-ignores · pylint-actions · pylint-json2html · lib-cli-exit-tools