-
Notifications
You must be signed in to change notification settings - Fork 707
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
Expand environment variables in URLs #640
Conversation
1bb1cc8
to
9f3ade3
Compare
2f81205
to
2c65561
Compare
be2d857
to
093fe73
Compare
2c65561
to
57161db
Compare
ffdda1b
to
fe08085
Compare
std::env::var(name).unwrap_or_else(|_| match name { | ||
"PROJECT_ROOT" => PROJECT_ROOT_FRAGMENT.clone(), |
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.
Is it intentional that PROJECT_ROOT
defined in the user env takes precedence over `PROJECT_ROOT?
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.
Yeah
098f220
to
2d86a8c
Compare
fe08085
to
62bd828
Compare
How it is possible to dynamically read the local package content like in poetry with Because for now, the only solution I found is to recompile the pypropject.toml with |
@alelavelli -- Are you looking for |
Yes but directly from the pyproject.toml. Something like poetry: [tool.poetry.dependencies] but with uv, like this: |
Unfortunately I think it's not possible in |
Summary
This PR enables users to express relative dependencies via environment variables. Like pip, PDM, Hatch, Rye, and others, we now allow users to express dependencies like:
In the compiled requirements file, we'll also preserve the unexpanded environment variable.
Closes #592.