uv export requirements-txt: requirements.txt starts with '-e .' and `uv pip install -r` fails outside the project dir with 'does not appear to be a Python project'
Add --no-emit-project to uv export --format requirements-txt so the file has no '-e .' line and installs from any directory. Without it, the first non-comment line (line 3, after the 2 autogenerated comment lines) is -e ., and uv pip install -r ../p1/requirements.txt run from a different directory fails with: error: /path/to/judge does not appear to be a Python project, as neither pyproject.toml nor setup.py are present in the directory (exit code 2). The . is resolved against the current working directory, not the requirements file's location. With --no-emit-project the same install into a plain uv venv env succeeded (7 packages, hashes kept). Tested with uv 0.12.6, Python 3.12.3 project (httpx 0.28.1), installing into a Python 3.14.7 venv.