Pytest Deprecation Lint (pytest 8 removals)
Marks the lines in your test suite that current pytest no longer runs — and the config keys it silently ignores.
Install
pytest-deprecation-lint file
Node 18+. The same 19 rules as the VS Code extension, from a terminal or CI.
Free
- Lint the test file, conftest.py or pytest config you have open and see every removed API and every silently ignored config key, each with the pytest version that removed it and the exact replacement line.
--ruleslists every rule
With a licence ($29 once)
- Sweep every test file, conftest.py and config file in the workspace in one pass and export the dated findings as Markdown or JSON you keep and paste into a CI job or a migration ticket.
@readystack/pytest-deprecation-lint --dir ./templates --report html --out report.html
A contract Python engineer reviewing the same suite for pytest 8 breakage by hand bills roughly $80-$120 an hour in the US market.
Use from an AI agent (MCP)
Claude Code · Cursor · Windsurf · any MCP client - add to your MCP config:
{ "mcpServers": { "pytest-deprecation-lint": { "command": "npx", "args": ["-y", "@readystack/pytest-deprecation-lint", "--mcp"] } } }
Tools: check_text and check_file (free) · check_dir (licence). The agent gets every finding with the line number.
Use in CI
- name: Pytest Deprecation Lint (pytest 8 removals)
run: npx -y @readystack/pytest-deprecation-lint --dir . --ci
(container: docker run --rm -v "$PWD:/work" getreadystack/pytest-deprecation-lint --dir /work --ci)
The folder sweep, reports and CI mode need one licence — one payment, no subscription. Set READYSTACK_LICENSE=<key> or run --license <key> once.
Install (PyPI)
pip install readystack-pytest-deprecation-lint
pytest-deprecation-lint --help
Metadata
Release files for readystack-pytest-deprecation-lint 1.0.4.post1
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 |
|---|---|---|---|---|
| readystack_pytest_deprecation_lint-1.0.4.post1.tar.gz | 11.8 kB | Without provenance | Details for readystack_pytest_deprecation_lint-1.0.4.post1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| readystack_pytest_deprecation_lint-1.0.4.post1-py3-none-any.whl | Python 3 | none | any | Details for readystack_pytest_deprecation_lint-1.0.4.post1-py3-none-any.whl |
Total release size: 25.3 kB
Release files / readystack_pytest_deprecation_lint-1.0.4.post1.tar.gz
| Download URL | readystack_pytest_deprecation_lint-1.0.4.post1.tar.gz |
|---|---|
| Size | 11.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6e3babd0ee1c50b42dd9be791a534683b817258f5f1a794b20e22242d28c10fd
|
|
BLAKE2b-256 checksum How to use checksums |
887620c2902cc730e7cb4a4f8167d23ab0ad612a82d90b95b98a5aaa1720089b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / readystack_pytest_deprecation_lint-1.0.4.post1-py3-none-any.whl
| Download URL | readystack_pytest_deprecation_lint-1.0.4.post1-py3-none-any.whl |
|---|---|
| Size | 13.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0dbe83ba9d130e211e92caef7b3796f5df9d978119491a4675200abfc03cb8dd
|
|
BLAKE2b-256 checksum How to use checksums |
09ad4238208521c7221a0c2aabe78b817c5c69073584e5887752e218677bad99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Security for readystack-pytest-deprecation-lint 1.0.4.post1
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.