Hi. Thanks a stack for conceiving uv. It is a true game changer in so many scenarios. 💯

Summary

requirements.txt files can reference dependencies of the local package at hand inside the working tree by using different option syntax like -e ., --editable ., or --editable=., iirc.

We are using the latter variant throughout our projects ¹, but it trips uv:

$ uv pip install -r docs/requirements.txt
error: Couldn't parse requirement in `docs/requirements.txt` at position 122
  Caused by: Expected package name starting with an alphanumeric character, found `=`
=.
^

Maybe this little report can help to make uv more universal in edge case situations like ours. It is certainly not a blocking issue for us, as we can easily update the offending line to use -e . instead of --editable=..

References

• uv pip install -r requirements.txt Fails to Parse Requirements #10417
• Support . for paths #1589
• Difference with pip on local non-editable installs #1827
• . only works with --editable #1499

Platform

Darwin 22.6.0 x86_64

Version

uv 0.5.23 (Homebrew 2025-01-23)

Python version

Python 3.13.1