Zeev Rotshtein
Zeev Rotshtein
Also, we already have a way to generate `requirements.txt` in the form of `uv pip compile` but it's rather tricky to have that match my `uv.lock`, especially if it's done...
I'm using this as a make-shift solution for now. ```sh uvx --from=yq tomlq -r '.package[]|.name+((.source|" @ "+(.url//"git+\(.git//empty)"))//"==\(.version)")' uv.lock >requirements.txt ```
The Python binaries `uv` installs were built using `clang` so they have `CC=clang` in their `sysconfig`. Thus, when using a `uv`-managed python when `clang` isn't available, `pip` also fails to...
``` CC=gcc CXX=g++ uv ... ```