From 671164c90a1ae0dcdb3676bfc2680331885ee054 Mon Sep 17 00:00:00 2001 From: p3ngu1nZz Date: Wed, 29 Jan 2025 05:35:02 -0500 Subject: [PATCH] Update UV lockfile handling instructions Improved the documentation comment regarding `.uv.lock` file inclusion in version control. The updated comment now emphasizes the importance of including `.uv.lock` for binary package reproducibility while also advising on ignoring it for libraries or packages that run in multiple environments. --- Python.gitignore | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/Python.gitignore b/Python.gitignore index 0a197900..c7fb09ab 100644 --- a/Python.gitignore +++ b/Python.gitignore @@ -82,6 +82,12 @@ target/ profile_default/ ipython_config.py +# uv +# Similar to Pipfile.lock and poetry.lock, it is recommended to include `.uv.lock` in version control. +# This ensures reproducibility, especially for binary packages. However, for libraries or packages that run in multiple environments, +# you might prefer to ignore this file and check it in only if necessary. +# .uv.lock + # pyenv # For a library or package, you might want to ignore these files since the code is # intended to run in multiple environments; otherwise, check them in: