[Onavo]

Also any machine learning use cases! There’s a big caveat with uv where they merge your Pipfile and pip installations. For example if you do uv add flask (this is added to pipfile) but then you need to add PyTorch with custom indexes (because most ML libraries distribute driver specific versions) and you do uv pip install PyTorch —-index-url what you end up with is a pipfile.lock that merges the two. uv won’t automatically add your dependency to the Pipfile.

https://pytorch.org/get-started/locally/

[baggiponte]

There's an issue about pytorch (I think you might already have seen it since you encountered this). This is still due to lack of support for pinning a package to a third party index (see https://github.com/astral-sh/uv/issues/171).

I am not sure I totally understand what you mean: yes, the lockfile might be messed up, but is the environment working? I'm a bit blessed because I don't have CUDA on my machine so I save myself a lot of hassle.

I am trying to submit an improvement to the docs about this. https://github.com/astral-sh/uv/pull/6523 I'd love to hear your feedback.

[Onavo]

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.

[baggiponte]

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/...

[Onavo]

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.