4 ms·
Unfortunately: > Some of uv's functionality cannot be expressed in the pylock.toml format; as such, uv will continue to use the uv.lock format within the proje
by JimDabell 1y ago
Unfortunately:
> Some of uv's functionality cannot be expressed in the pylock.toml format; as such, uv will continue to use the uv.lock format within the project interface.
> However, uv supports pylock.toml as an export target and in the uv pip CLI.
— https://docs.astral.sh/uv/concepts/projects/layout/#the-lockfile https://docs.astral.sh/uv/concepts/projects/layout/#the-lock...
- testdelacc1 1y agoThat is pretty unfortunate. Would have been cool if all of them could have used the same file. Of course there must have been really good reasons for this decision. I hope no one will hold it against the maintainers of any of the projects. Especially because it looks like it is easy to move between the two lock files.
- sirodoht 1y agoWhich functionality of uv's cannot be expressed in the pylock.toml format?
- maleldil 1y agoMore information here: https://github.com/astral-sh/uv/issues/12584 https://github.com/astral-sh/uv/issues/12584 > The biggest limitation is that there's no support for arbitrary entrypoints to the graph, because pylock.toml includes a fixed marker for each package entry rather than recording a graph of dependencies.