-
Notifications
You must be signed in to change notification settings - Fork 760
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
Recursive extra dependencies don't compile like pip-tools #1987
Labels
bug
Something isn't working
Comments
I thought I fixed this but I'll take another look. |
Ahh this is slightly different, you're passing the |
|
charliermarsh
added a commit
that referenced
this issue
Feb 26, 2024
## Summary When a `pyproject.toml` is provided directly to `uv pip compile`, we were failing to resolve recursive extras. The solution I settled on here is to flatten them recursively when determining the requirements upfront. Closes #1987. ## Test Plan `cargo test`
Fixed in the next release, thanks. |
Thanks for the quick fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Essentially the same issue as jazzband/pip-tools#1685. When you have a recursive extras in a
pyproject.toml
for a private project,uv pip compile
fails. If the project is uploaded to an index, then it looks in the index first, but I'd expect it to prioritize the self-reference inpyproject.toml
.Info
uv pip compile pyproject.toml --extra=dev
Reproducible example (from pip-tools issue)
Minimal
pyproject.toml
With pip-tools, this is the output:
With uv, this is the output:
❯ uv pip compile pyproject.toml --extra=dev × No solution found when resolving dependencies: ╰─▶ Because privateproject[test] was not found in the package registry and privateproject depends on privateproject[test], we can conclude that the requirements are unsatisfiable.
The text was updated successfully, but these errors were encountered: