Skip to content

Pin the lint contract: explicit rule set, bounded ruff #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
keithadler wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Pin the lint contract: explicit rule set, bounded ruff #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 9 additions & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ classifiers = [
]

[project.optional-dependencies]
dev = ["pytest>=8", "ruff>=0.4", "flake8>=7"]
dev = ["pytest>=8", "ruff>=0.4,<0.17", "flake8>=7"]

[project.scripts]
exact = "exact_linter.cli:main"
Expand All @@ -42,3 +42,11 @@ testpaths = ["tests"]
[tool.ruff]
line-length = 100
target-version = "py310"

[tool.ruff.lint]
# State the rule set explicitly rather than inheriting ruff's default, which
# is not stable across releases: 0.16 widened it to include isort, pylint,
# flake8-simplify and flake8-blind-except, and CI started failing on code
# that had not changed. The blind `except Exception` around eval()/pslq() is
# deliberate - a linter must degrade to None, never crash on user input.
select = ["E4", "E7", "E9", "F"]
Loading