Hatch support for uv.lock

[RickyDaMa]

Does Hatch support/respect uv's lockfile, or are there any plans to add this? I don't believe Hatch has its own lock file standard currently

[funkyfuture]

there's a proposal for a standard lock file spec.

[sathieu]

PEP 751 is about [project]'s dependencies. Is there anything about [tool.hatch.envs.<envname>] dependencies and extra-dependencies?

[juftin]

PEP 751 is about [project]'s dependencies. Is there anything about [tool.hatch.envs.<envname>] dependencies and extra-dependencies?

Sorry for lurking, but I wanted to point out an important distinction between Hatch and UV and their differing approaches to "environments."

UV supports a singular virtual environment with a corresponding LockFile. UV supports different dependency groups for the environment (like "dev" / "test" / "docs"), however each of these groups ultimately need to resolve to the same virtual environment and the same LockFile.

Hatch, on the other hand, uses a virtual-environment-per-environment approach instead of dependency groups. This means that you would have a different virtual environment for each of your "dev" / "test" / "docs" environments. The power here of Hatch's approach is that you can have conflicting versions across your environments. Environment A can use pandas==1.0.0 and Environment B can use pandas==2.0.0.

As things stand today, in order for Hatch to support UV LockFiles there would need to be a LockFile per-environment.

From my understanding, hatch is also standards-based so I believe that the UV LockFile would need to be fully standardized and accepted before Hatch would adopt it (I don't represent the viewpoints of the Hatch maintainers so take this comment at face-value).