-
Notifications
You must be signed in to change notification settings - Fork 614
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
How to convert requirements.txt to tool.uv.sources
?
#6275
Comments
Well, we should support this with e.g.
|
Needs documentation still. |
Just an idea, can we instead add a new flag My specific use case is using Apache Airflow which only supports That way, I can do (copying from their example):
|
Or, thinking aloud, more broadly are there any other flags that exist in |
@yehoshuadimarsky can you please open a dedicated issue for that request? You need to add that constraint file to |
The problem with If a Basically need this, without saving any constraints to
Doesn't have to be |
The typically workaround (which isn't very nice) is:
uv will then avoid upgrading past the pinned versions in the future by default. \cc @zanieb since we've discussed this in-person before. |
Thanks for the tip, but do you plan on handling this automatically? Just considering what to put in our docs. |
With pip I use constraints files containing a bunch of git URLs to achieve the equivalent of
tool.uv.sources
.Is there a convenient way to convert such a requirements file to a
tool.uv.sources
section?The text was updated successfully, but these errors were encountered: