--- id: pylint-pytest version: "1.1.8" license: MIT license_treatment: permissive maintenance: active --- # pylint-pytest — A Pylint plugin to suppress pytest-related false positives. License: permissive · Maintenance: active · Downloads: 600.6K/mo ## What it is and what it does pylint-pytest is a Pylint plugin designed to make static analysis work better with pytest test code. It solves the problem of Pylint raising false-positive warnings when analyzing pytest fixtures and test functions—for example, flagging fixture parameters as unused arguments even though pytest injects them at runtime. The plugin suppresses four common false positives (unused-argument, unused-import, redefined-outer-name, and no-member) that occur when fixtures are properly used but not referenced in the function body. Beyond suppression, the plugin also raises four new warnings to catch deprecated or problematic pytest patterns: deprecated-pytest-yield-fixture (for the old @pytest.yield_fixture decorator), useless-pytest-mark-decorator (for @pytest.mark.* on fixtures where it has no effect), deprecated-positional-argument-for-pytest-fixture (for positional arguments to @pytest.fixture), and cannot-enumerate-pytest-fixtures (when the plugin cannot analyze fixtures in a test module). It requires pylint and pytest>=4.6 and is enabled by loading it as a Pylint plugin. Use it for: - Suppress false positives in CI/CD pipelines that run Pylint on pytest test suites to maintain a clean lint report. - Catch deprecated pytest patterns like @pytest.yield_fixture before they cause issues in newer pytest versions. - Analyze fixture-heavy test code without having to disable Pylint rules or add noqa comments throughout. - Enforce consistent pytest fixture patterns by raising warnings on useless decorators or positional arguments. - Integrate code quality checks into test modules without fighting Pylint's static analysis limitations. ## Worth the install? AI-flagged interpretation of the facts above — verify before relying. A Pylint plugin that suppresses false-positive warnings when analyzing pytest test code, and raises new warnings for deprecated or problematic pytest patterns. Yes. This is a low-friction, actively maintained plugin that solves a real problem: Pylint's inability to understand pytest's fixture injection model. If you run Pylint on pytest test code, this plugin will eliminate noise and catch genuine pytest anti-patterns. No security issues, permissive license, and production-stable. ## Install pip install pylint-pytest uv add pylint-pytest poetry add pylint-pytest ## Installing pylint-pytest Before you install: Low friction install with just two runtime dependencies (pylint and pytest). Actively maintained with a recent commit in 2026 and marked as production-stable. License in practice: MIT license is permissive; you can use this in commercial and proprietary projects with minimal restrictions. Quickstart: pip install pylint-pytest # In .pylintrc: # [MASTER] # load-plugins=pylint_pytest # Or via command line: # pylint --load-plugins pylint_pytest Verify before relying: - Whether the plugin correctly handles all pytest fixture patterns in real-world test suites - Performance impact when analyzing large test codebases with many fixtures ## Package facts - License: MIT (permissive) - Python support: supports_current - Install friction: low - Maintenance: active - Downloads: 600.6K/month (top 15,000 on PyPI) - Known vulnerabilities: none known ## Tags pylint pytest plugin, suppress pylint false positives, pytest fixture linting, pylint pytest integration, fixture unused argument warning, pytest code quality checks, pylint test code analysis, pytest-integration, linting, code-quality [View on SkillFed](https://skillfed.io/packages/pylint-pytest) · [View on PyPI](https://pypi.org/project/pylint-pytest/)