-
Notifications
You must be signed in to change notification settings - Fork 682
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 build-constraints
support to uv lock
etc. via pyproject.toml
#6913
Comments
I could have a look to this @charliermarsh. |
Go for it! |
@menkotoglou -- Just let me know if you're not able or don't plan to get to it (or need some pointers!), so we can prioritize accordingly. |
Hey @charliermarsh, sorry for not taking it on this week, some stuff came up and didn't have time to take it on. Was actually planning to start working on it this week, and of course revert back to you if any help needed. Wdyt? |
I am trying to understand if this is the feature I need. My problem:
This is the most sane way I could find so both requirements.txt and requirements-dev.txt contain the same libs except for the dev ones and they respect the constraints file which are sub dependencies I need to limit but do not depend myself. I want to move to From the docs:
It seems I would like to perform 2 things:
Eventually I will remove the exports, but for validating the process, I will need to make sure the output versions are identical to the original versions Is this the correct issue? |
Ok, I found a workaround. If I set
UV will enforce the optional dependencies when resolving the lock.
Edit: I leave this here in case anyone else wants to migrate from pip compile to uv lock |
Can follow the way we manage
constraint-dependencies.
See: #5561 (comment).
The text was updated successfully, but these errors were encountered: