From f1479626f3c2f2632504227524ccd46ba21e1904 Mon Sep 17 00:00:00 2001 From: John E Date: Mon, 10 Nov 2025 13:11:13 -0500 Subject: [PATCH] Propose fix typo and ignore emacs backup files Signed-off-by: John E --- .gitignore | 2 ++ sdata/uv/README.md | 2 +- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index cef4d7aab..b59d26bf8 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,5 @@ __pycache__/ dots/.config/quickshell/ii/.qmlls.ini .update-lock /os-release +#emacs backup +*~ diff --git a/sdata/uv/README.md b/sdata/uv/README.md index 700f25772..8172c7c9b 100644 --- a/sdata/uv/README.md +++ b/sdata/uv/README.md @@ -13,7 +13,7 @@ This is important because there has been so many complaints about the failure in - For reference see [uv doc](https://docs.astral.sh/uv/pip/dependencies/#using-requirementsin). - `requirements.txt` is included in Git. It's for locking package versions to enhance stability and reproducibility.[^1] -[^1]: In fact, including package version lock file in Git is also the most common way for similar situations, for example the `package-lock.json` of Node.js projects (see also [this stackoverflow question](https://stackoverflow.com/questions/48524417/should-the-package-lock-json-file-be-added-to-gitignore)). Although there are some situations when it's not suitable to include the lock file, for example [the poetry document](https://python-poetry.org/docs/basic-usage/#committing-your-poetrylock-file-to-version-control) recommend application developers to include package version lock file in Git, but library developers should consider more, such as not inluding the lock file or including it but refreshing regularly. +[^1]: In fact, including package version lock file in Git is also the most common way for similar situations, for example the `package-lock.json` of Node.js projects (see also [this stackoverflow question](https://stackoverflow.com/questions/48524417/should-the-package-lock-json-file-be-added-to-gitignore)). Although there are some situations when it's not suitable to include the lock file, for example [the poetry document](https://python-poetry.org/docs/basic-usage/#committing-your-poetrylock-file-to-version-control) recommend application developers to include package version lock file in Git, but library developers should consider more, such as not including the lock file or including it but refreshing regularly. ## How will the python packages get installed?