Skip to content
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

Merged
merged 12 commits into from
Dec 12, 2024
Merged

Add pip compile #984

merged 12 commits into from
Dec 12, 2024

Conversation

neob91-close
Copy link
Contributor

@neob91-close neob91-close commented Dec 10, 2024

I just wanted to introduce pip-compile, but had to switch to ruff 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.

@neob91-close neob91-close force-pushed the add-pip-compile branch 3 times, most recently from 79fa359 to c73e857 Compare December 10, 2024 11:01
@neob91-close neob91-close marked this pull request as ready for review December 10, 2024 11:13
@neob91-close neob91-close force-pushed the add-pip-compile branch 10 times, most recently from 64c1991 to 6451ade Compare December 11, 2024 15:59
@neob91-close
Copy link
Contributor Author

neob91-close commented Dec 11, 2024

Now I'm thinking maybe I should just swap out the current *.txt requirements files for the autogenerated ones as a separate PR.

That shouldn't block the review of this PR though.

Copy link
Contributor

@squeaky-pl squeaky-pl left a 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.

@tsx
Copy link
Contributor

tsx commented Dec 12, 2024

I just wish we didn't have to do it all in one PR.

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.

@tsx tsx removed their request for review December 12, 2024 06:31
@wojcikstefan
Copy link
Member

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 👍

@neob91-close neob91-close mentioned this pull request Dec 12, 2024
@neob91-close
Copy link
Contributor Author

Ruff PR: #985

@neob91-close
Copy link
Contributor Author

Removed the ruff-related changes, and regenerated the requirements files.

@neob91-close neob91-close merged commit 337a273 into master Dec 12, 2024
4 checks passed
@neob91-close neob91-close deleted the add-pip-compile branch December 12, 2024 12:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants