---
id: pylint-exit
version: "1.2.0"
license: unclear
license_treatment: permissive
maintenance: abandoned
---

# pylint-exit — Exit code handler for pylint command line utility.

License: permissive · Maintenance: abandoned · Downloads: 156.5K/mo

## 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 above — verify before relying.

Translates pylint's bit-encoded exit codes into scripting-friendly return codes (0 or 1) for use in shell scripts and CI pipelines.

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

pip install pylint-exit
uv add pylint-exit
poetry add pylint-exit

## Installing pylint-exit

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
fi

Verify 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: not declared (permissive)
- Python support: unspecified
- Install friction: low
- Maintenance: abandoned
- Downloads: 156.5K/month (top 15,000 on PyPI)
- Known vulnerabilities: none known

## Tags

pylint exit code handler, shell script pylint integration, ci pylint return code, decode pylint exit codes, pylint scripting wrapper, ci-integration, shell-scripting

[View on SkillFed](https://skillfed.io/packages/pylint-exit) · [View on PyPI](https://pypi.org/project/pylint-exit/)