I think the docs should be more clear that the uv pip command is an escape hatch, and the moment you use it you basically lose the ability to have the Pipfile as a source of truth. Most devs won't be looking too closely at the lockfile unless it's to debug issues, they usually only refer to the Pipfile. It would also be nice to have a pip to uv/rye command converter like those curl command generators.

I wouldn't say it's an escape hatch: pip and poetry/pdm/uv serve different purposes. I am not sure what you refer to with `Pipfile`. As per the "command converter": you mean something like from `uv pip` to `uv add`?

BTW, there is a proposal to standardise the lockfile format in Python: https://discuss.python.org/t/pep-751-lock-files-again/59173/...

Yes, a command converter as you described (that supports converting all the pip flags and command parameters) would be very useful. At the end of the day, you need a (readable) single source of truth somewhere (i.e. not the lockfile, the lockfile is fine for deployment and operations but not for developers). As a developer, I don't want the `uv pip` commands to mess up my environment, but at the same time, 90% of the Python world assumes dependency management is done with pip, and when I am installing dependencies, I don't really have time to chase down the exact flags that I should be using to add it to the Pipfile and to ensure uv compatibility.