-
Notifications
You must be signed in to change notification settings - Fork 148
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.
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
Modernise tooling and fix CI failing #335
Conversation
d1bc119
to
d66558b
Compare
Failing flake8 looks like this: python/importlib_metadata#406 :( |
This is an exc
Good spot, thank you. This is an excellent excuse for us to move to ruff instead of flake8. |
d66558b
to
8b21f0f
Compare
6cbfadf
to
24b06ea
Compare
There is one unit test failing. I can't obviously see why it's failing. |
Sorry. |
No worries. It's easily done, and was our fault for having broken CI. |
Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
IDK we sometimes have to invoke trial explicitly like this
And remove py2-style type annotations, which ruff doesn't recognise Co-authored-by: Patrick Cloke <clokep@users.noreply.github.com>
Needed for unit tests to be happy
73feb4f
to
afe3d2e
Compare
Commitwise reviewable.
I think the only necessary changes were
In particular, moving to pyproject.toml was my first attempt/guess to fix the CI errors, but I don't think it was strictly necessary.