-
Notifications
You must be signed in to change notification settings - Fork 889
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
uv pip compile
does not respect tool.setuptools.dynamic
dependencies
#1644
Comments
Related: #1624 |
I've also run into this issue and I just wanted to +1 this feature. In my case I have something like:
and then all the dependencies in |
We will address this as discussed in #1624 |
For what it's worth, if you treat the project as a dependency, we should respect it. E.g. |
I've temporarily fixed this just by using directly (which is not a big deal)
It is a little less convenient for extras, i.e.
instead of (this does not work)
(assuming you also have |
I'll be looking into this tomorrow. |
Now in review here: #2633. Expect it to be supported in the next release. |
## Summary When a user passes a `pyproject.toml` to `pip compile` (e.g., `uv pip compile pyproject.toml`), we extract the requirements from the `pyproject.toml` directly. However... that isn't always possible (as seen in the linked issues). When it's _not_, we instead need to run the PEP 517 build hooks to identify the metadata. Closes #1624. Closes #1644. ## Test Plan `cargo test`
With the following files,
pip-compile
output includes theruff
dependency,uv pip compile
does not:pyproject.toml
:requirements.txt
:pip-compile
includesruff
:uv
does not:I expect
uv
's behaviour to matchpip-compile
's, or for the difference to be documented.The text was updated successfully, but these errors were encountered: