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

chore: deprecate pip-compile-multi in favor or uv #31313

Merged
merged 13 commits into from
Dec 19, 2024
Merged

Conversation

mistercrunch
Copy link
Member

pip-compile-multi hasn't been working super well for us. It has a few bugs, is pretty slow, and turns out uv supports our use case much better and at blazing speeds.

@github-actions github-actions bot added doc Namespace | Anything related to documentation github_actions Pull requests that update GitHub Actions code labels Dec 5, 2024
@mistercrunch mistercrunch added the v5.0 Label added by the release manager to track PRs to be included in the 5.0 branch label Dec 9, 2024
@mistercrunch mistercrunch changed the title chore: deprecate pip-compile-multi in fabov or uv chore: deprecate pip-compile-multi in favor or uv Dec 18, 2024
@rusackas
Copy link
Member

/korbit-review

Copy link

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review by Korbit AI

Category Issue
Functionality Incorrect Input File Specification for Base Requirements ▹ view
Functionality Missing UV Command Validation ▹ view
Files scanned
File Path Reviewed
scripts/uv-pip-compile.sh

Explore our documentation to understand the languages and file types we support and the files we ignore.

Need a new review? Comment /korbit-review on this PR and I'll review your latest changes.

Korbit Guide: Usage and Customization

Interacting with Korbit

  • You can manually ask Korbit to review your PR using the /korbit-review command in a comment at the root of your PR.
  • You can ask Korbit to generate a new PR description using the /korbit-generate-pr-description command in any comment on your PR.
  • Too many Korbit comments? I can resolve all my comment threads if you use the /korbit-resolve command in any comment on your PR.
  • Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
  • Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.

Customizing Korbit

  • Check out our docs on how you can make Korbit work best for you and your team.
  • Customize Korbit for your organization through the Korbit Console.

Current Korbit Configuration

General Settings
Setting Value
Review Schedule Automatic excluding drafts
Max Issue Count 10
Automatic PR Descriptions
Issue Categories
Category Enabled
Naming
Database Operations
Documentation
Logging
Error Handling
Systems and Environment
Objects and Data Structures
Readability and Maintainability
Asynchronous Processing
Design Patterns
Third-Party Libraries
Performance
Security
Functionality

Feedback and Support

Note

Korbit Pro is free for open source projects 🎉

Looking to add Korbit to your team? Get started with a free 2 week trial here

Comment on lines 24 to 25
# Generate the requirements/base.txt file
uv pip compile pyproject.toml -c requirements/base.in -o requirements/base.txt $ADDITIONAL_ARGS
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect Input File Specification for Base Requirements category Functionality

Tell me more
What is the issue?

The first command uses requirements/base.in as a constraint (-c) while it should be using it as an input file since it's the primary source for base.txt.

Why this matters

Using base.in as a constraint instead of an input file means the dependencies specified in base.in might not be properly included in the final requirements file, potentially leading to missing dependencies.

Suggested change

Replace the first command with:
uv pip compile pyproject.toml requirements/base.in -o requirements/base.txt $ADDITIONAL_ARGS

Chat with Korbit by mentioning @korbit-ai, and give a 👍 or 👎 to help Korbit improve your reviews.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mistercrunch is this accurate? ¯\_(ツ)_/¯

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

requirements.in really is used as a set of constraints here, the name might be confusing though. I could rename to base-constraints.txt for clarity

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could probably also merge the constraints in pyproject.toml so it's all in one place

scripts/uv-pip-compile.sh Show resolved Hide resolved
@mistercrunch mistercrunch merged commit 9da65d6 into master Dec 19, 2024
37 checks passed
@mistercrunch mistercrunch deleted the uv_pip_compile branch December 19, 2024 01:41
@andy-clapson
Copy link
Contributor

Hey @mistercrunch very nice to see! It's crazy fast, hey?

tmsjordan pushed a commit to tmsdevelopment/superset that referenced this pull request Feb 1, 2025
@michael-s-molina michael-s-molina removed the v5.0 Label added by the release manager to track PRs to be included in the 5.0 branch label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Namespace | Anything related to documentation github_actions Pull requests that update GitHub Actions code preset-io size/XXL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants