You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running uv pip install -r requirements.txt fails with a parsing error, while pip install -r requirements.txt works without issues.
requirements.txt content:
--editable '.[dev]'
Error Output:
Running uv pip install -r requirements.txt produces the following error:
error: Couldn't parse requirement in `requirements.txt` at position 11
Caused by: Expected package name starting with an alphanumeric character, found `'`
'.[dev]'
^
However, pip install -r requirements.txt successfully installs the requirements.
uv version: 0.5.16
The text was updated successfully, but these errors were encountered:
We don't support stringified dependencies like that. You can just remove the quotes -- they aren't needed in a requirements.txt file.
Without the quotes uv pip works; however, pip fails with the following error:
ERROR: .[dev, is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with
bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http,
hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).
I reckon this difference in behavior should be documented in the pip compatibility section.
Running
uv pip install -r requirements.txt
fails with a parsing error, whilepip install -r requirements.txt
works without issues.requirements.txt
content:Error Output:
Running
uv pip install -r requirements.txt
produces the following error:However,
pip install -r requirements.txt
successfully installs the requirements.uv version: 0.5.16
The text was updated successfully, but these errors were encountered: