GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||
GeezerVison is showing github.com — Lint tests by roryyorke · Pull Request #1127 · python-control/python-control Conversation
Contributor
This extends ruff testing to control/tests/*.py I've tried to order the commits from obvious to subtle; on the whole:
The remaining errors I'm less sure of. It would be simple to silence them with More detail on remaining failures:
|
|
coverage: 94.744%. remained the same |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
Correct that there just needs to be some test that verifies that unknown keywords generate an error. Whichever of the tests that has that check should be kept and if both do then keeping either is fine.
Correct that the intent of this test was just to make sure an exception wasn't raised. We could either get rid of the assignment to
I'm pretty sure I wrote this example and I can't see any reason to keep |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
This reverts commit 5ff3c0c.
|
Oops - had a commit there I'd intended for another PR. Reverted. If this PR isn't merged now, it'll be worth merging main into the PR before merging the PR to main, to make sure the lint checks don't causes failures on main after the merge of the PR. (I hope that sentence is less confusing than I think it is!) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.