-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add pip compile #984
Add pip compile #984
Conversation
79fa359
to
c73e857
Compare
64c1991
to
6451ade
Compare
Now I'm thinking maybe I should just swap out the current That shouldn't block the review of this PR though. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The general structure looking good. Not reviewing machine generated changes.
What's stopping you from shipping ruff changes separately first? Doing both ruff and dependency resolver change seems like an insane amount of risk to me. |
I'm not sure if I'd call it "insane", but I agree it's a bit too much of a risk and that if we can easily ship ruff first, it would help 👍 |
Ruff PR: #985 |
6451ade
to
4ed08f1
Compare
Removed the ruff-related changes, and regenerated the requirements files. |
I just wanted to introduce
pip-compile
, but had to switch toruff
as well, because we had some conflicting linting packages, and after fixing that, flake8 started reporting a whole lot of different errors.We were going to introduce
ruff
anyway, I just wish we didn't have to do it all in one PR.Definitely review commits separately.