-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 freezes vcs subdirectory requirements in non-roundtrippable format #1931
Comments
👍 This is a bug. There's another issue for it somewhere... |
Can't find it, so we'll just track this here. |
Thanks for confirming I wasn't holding it wrong! |
I swear it's somewhere 😂 But it might be buried. |
I was going to submit a PR for this myself, but tbh would not have figured out the test harness changes you implemented in #1936. Thanks for the fix! |
No prob, thanks for reporting @mqudsi! |
Apologies in advance if I'm missing something as I'm primarily a low-level (rust + others) dev and speaking from a position of little production Python experience here.
Installing a package via the
vcs+https://
protocol and specifying both a revision and a subdirectory results in a subsequentuv pip freeze
output that seems to include the entry in a human-readable rather than machine-parseable format. If piped torequirements.txt
then fed back into eitheruv
orpip
([uv] pip install -r requirements.txt
), this always fails to install as it does not understand the syntax.Reproduction:
Resulting in
Attempting to install the generated
requirements.txt
withpip
results in the following error:while attempting to install with
uv
also fails:whereas it seems that a
requirements.txt
entry in the following format is supported by bothpip
anduv pip
:so presumably this is what
uv pip freeze
should emit?Running
uv
v0.1.10 andpip
v23.3.1The text was updated successfully, but these errors were encountered: