Pin the formatter to the ruff 0.17 line
Dependabot offered #33, which let both 0.16 and 0.17 in. A range of two minor lines lets CI and a laptop use different formatters, which is the problem that the pin prevents. Thus the pin moves to the 0.17 line, and the floor is 0.17.1. Ruff 0.17.1 and 0.17.3 find nothing new in the committed tree. The breaking change of 0.17 is a new default Python version, and `target-version = "py310"` already sets ours. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
763eec5de9
commit
44a7519681
1 file changed
+1
-1
+1
-1
@@ -58,7 +58,7 @@ dev = [
|
||||
# The version is pinned to one minor line. A formatter that is different on different
|
||||
# machines is not a gate. Ruff 0.16 formats Python inside Markdown and 0.15 does not.
|
||||
# With an unpinned `ruff>=0.4`, CI and a laptop disagreed about a tree with no errors.
|
||||
"ruff>=0.16.6,<0.17",
|
||||
"ruff>=0.17.1,<0.18",
|
||||
# The node of the SPI radio. tests/test_radionode_live.py runs it with a fake radio.
|
||||
# The library alone is pure Python on all systems. Only the `hardware` extra needs Linux.
|
||||
"openhop-core>=1.1.3",
|
||||
|
||||
Reference in new issue
Block a user