[pre-commit.ci] pre-commit autoupdate (#221)

pre-commit-ci[bot] · github-actions[bot] · web-flow · commit 316a7d310746 · 2025-02-07T09:00:33.000-08:00
* [pre-commit.ci] pre-commit autoupdate updates: - [github.com/astral-sh/ruff-pre-commit: v0.8.6 → v0.9.4](astral-sh/ruff-pre-commit@v0.8.6...v0.9.4) * [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci * Update files from markdown-code-runner --------- Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -7,7 +7,7 @@ repos:
       - id: end-of-file-fixer
       - id: mixed-line-ending
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: "v0.8.6"
+    rev: "v0.9.4"
     hooks:
       - id: ruff
         args: ["--fix"]
diff --git a/README.md b/README.md
@@ -420,8 +420,7 @@ See [example](example/) for more information or check the output of `unidep -h`
 <!-- ⚠️ This content is auto-generated by `markdown-code-runner`. -->
 ```bash
 usage: unidep [-h]
-              {merge,install,install-all,conda-lock,pip-compile,pip,conda,version}
-              ...
+              {merge,install,install-all,conda-lock,pip-compile,pip,conda,version} ...
 
 Unified Conda and Pip requirements management.
 
@@ -498,23 +497,22 @@ can also just run `unidep merge`.
 
 options:
   -h, --help            show this help message and exit
-  -o OUTPUT, --output OUTPUT
-                        Output file for the conda environment, by default
+  -o, --output OUTPUT   Output file for the conda environment, by default
                         `environment.yaml`
-  -n NAME, --name NAME  Name of the conda environment, by default `myenv`
+  -n, --name NAME       Name of the conda environment, by default `myenv`
   --stdout              Output to stdout instead of a file
   --selector {sel,comment}
                         The selector to use for the environment markers, if
                         `sel` then `- numpy # [linux]` becomes `sel(linux):
                         numpy`, if `comment` then it remains `- numpy #
                         [linux]`, by default `sel`
-  -d DIRECTORY, --directory DIRECTORY
+  -d, --directory DIRECTORY
                         Base directory to scan for `requirements.yaml` or
                         `pyproject.toml` file(s), by default `.`
   --depth DEPTH         Maximum depth to scan for `requirements.yaml` or
                         `pyproject.toml` files, by default 1
   -v, --verbose         Print verbose output
-  -p {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
+  -p, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
                         The platform(s) to get the requirements for. Multiple
                         platforms can be specified. By default, the current
                         platform (`linux-64`) is used.
@@ -555,8 +553,9 @@ usage: unidep install [-h] [-v] [-e] [--skip-local] [--skip-pip]
                       [--skip-conda] [--skip-dependency SKIP_DEPENDENCY]
                       [--no-dependencies]
                       [--conda-executable {conda,mamba,micromamba}]
-                      [-n CONDA_ENV_NAME | --conda-env-prefix CONDA_ENV_PREFIX]
-                      [--dry-run] [--ignore-pin IGNORE_PIN]
+                      [-n CONDA_ENV_NAME |
+                      --conda-env-prefix CONDA_ENV_PREFIX] [--dry-run]
+                      [--ignore-pin IGNORE_PIN]
                       [--overwrite-pin OVERWRITE_PIN] [-f CONDA_LOCK_FILE]
                       [--no-uv]
                       files [files ...]
@@ -601,7 +600,7 @@ options:
                         installed.
   --conda-executable {conda,mamba,micromamba}
                         The conda executable to use
-  -n CONDA_ENV_NAME, --conda-env-name CONDA_ENV_NAME
+  -n, --conda-env-name CONDA_ENV_NAME
                         Name of the conda environment, if not provided, the
                         currently active environment name is used, unless
                         `--conda-env-prefix` is provided
@@ -619,7 +618,7 @@ options:
                         e.g., `--overwrite-pin 'numpy=1.19.2'`. This option
                         can be repeated to overwrite the pins of multiple
                         packages.
-  -f CONDA_LOCK_FILE, --conda-lock-file CONDA_LOCK_FILE
+  -f, --conda-lock-file CONDA_LOCK_FILE
                         Path to the `conda-lock.yml` file to use for creating
                         the new environment. Assumes that the lock file
                         contains all dependencies. Must be used with `--conda-
@@ -647,8 +646,9 @@ usage: unidep install [-h] [-v] [-e] [--skip-local] [--skip-pip]
                       [--skip-conda] [--skip-dependency SKIP_DEPENDENCY]
                       [--no-dependencies]
                       [--conda-executable {conda,mamba,micromamba}]
-                      [-n CONDA_ENV_NAME | --conda-env-prefix CONDA_ENV_PREFIX]
-                      [--dry-run] [--ignore-pin IGNORE_PIN]
+                      [-n CONDA_ENV_NAME |
+                      --conda-env-prefix CONDA_ENV_PREFIX] [--dry-run]
+                      [--ignore-pin IGNORE_PIN]
                       [--overwrite-pin OVERWRITE_PIN] [-f CONDA_LOCK_FILE]
                       [--no-uv]
                       files [files ...]
@@ -693,7 +693,7 @@ options:
                         installed.
   --conda-executable {conda,mamba,micromamba}
                         The conda executable to use
-  -n CONDA_ENV_NAME, --conda-env-name CONDA_ENV_NAME
+  -n, --conda-env-name CONDA_ENV_NAME
                         Name of the conda environment, if not provided, the
                         currently active environment name is used, unless
                         `--conda-env-prefix` is provided
@@ -711,7 +711,7 @@ options:
                         e.g., `--overwrite-pin 'numpy=1.19.2'`. This option
                         can be repeated to overwrite the pins of multiple
                         packages.
-  -f CONDA_LOCK_FILE, --conda-lock-file CONDA_LOCK_FILE
+  -f, --conda-lock-file CONDA_LOCK_FILE
                         Path to the `conda-lock.yml` file to use for creating
                         the new environment. Assumes that the lock file
                         contains all dependencies. Must be used with `--conda-
@@ -773,18 +773,18 @@ options:
   --check-input-hash    Check existing input hashes in lockfiles before
                         regenerating lock files. This flag is directly passed
                         to `conda-lock`.
-  -d DIRECTORY, --directory DIRECTORY
+  -d, --directory DIRECTORY
                         Base directory to scan for `requirements.yaml` or
                         `pyproject.toml` file(s), by default `.`
   --depth DEPTH         Maximum depth to scan for `requirements.yaml` or
                         `pyproject.toml` files, by default 1
-  -f FILE, --file FILE  A single `requirements.yaml` or `pyproject.toml` file
+  -f, --file FILE       A single `requirements.yaml` or `pyproject.toml` file
                         to use, or folder that contains that file. This is an
                         alternative to using `--directory` which searches for
                         all `requirements.yaml` or `pyproject.toml` files in
                         the directory and its subdirectories.
   -v, --verbose         Print verbose output
-  -p {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
+  -p, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
                         The platform(s) to get the requirements for. Multiple
                         platforms can be specified. By default, the current
                         platform (`linux-64`) is used.
@@ -849,16 +849,16 @@ positional arguments:
 
 options:
   -h, --help            show this help message and exit
-  -o OUTPUT_FILE, --output-file OUTPUT_FILE
+  -o, --output-file OUTPUT_FILE
                         Output file for the pip requirements, by default
                         `requirements.txt`
-  -d DIRECTORY, --directory DIRECTORY
+  -d, --directory DIRECTORY
                         Base directory to scan for `requirements.yaml` or
                         `pyproject.toml` file(s), by default `.`
   --depth DEPTH         Maximum depth to scan for `requirements.yaml` or
                         `pyproject.toml` files, by default 1
   -v, --verbose         Print verbose output
-  -p {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
+  -p, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
                         The platform(s) to get the requirements for. Multiple
                         platforms can be specified. By default, the current
                         platform (`linux-64`) is used.
@@ -911,11 +911,11 @@ file.
 
 options:
   -h, --help            show this help message and exit
-  -f FILE, --file FILE  The `requirements.yaml` or `pyproject.toml` file to
+  -f, --file FILE       The `requirements.yaml` or `pyproject.toml` file to
                         parse, or folder that contains that file, by default
                         `.`
   -v, --verbose         Print verbose output
-  -p {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
+  -p, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
                         The platform(s) to get the requirements for. Multiple
                         platforms can be specified. By default, the current
                         platform (`linux-64`) is used.
@@ -970,11 +970,11 @@ to specify multiple `requirements.yaml` or `pyproject.toml` files and that
 
 options:
   -h, --help            show this help message and exit
-  -f FILE, --file FILE  The `requirements.yaml` or `pyproject.toml` file to
+  -f, --file FILE       The `requirements.yaml` or `pyproject.toml` file to
                         parse, or folder that contains that file, by default
                         `.`
   -v, --verbose         Print verbose output
-  -p {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
+  -p, --platform {linux-64,linux-aarch64,linux-ppc64le,osx-64,osx-arm64,win-64}
                         The platform(s) to get the requirements for. Multiple
                         platforms can be specified. By default, the current
                         platform (`linux-64`) is used.
diff --git a/example/README.md b/example/README.md
@@ -110,11 +110,11 @@ Using `unidep` for installation offers a more comprehensive approach. It handles
 $ unidep install --dry-run -e ./setup_py_project
 📦 Installing conda dependencies with `conda install --yes --override-channels --channel conda-forge pandas">=1,<3" adaptive">=0.15.0, <2.0.0" pfapack packaging adaptive-scheduler numpy">=1.21" hpc05 pexpect pytest pytest-cov`
 
-📦 Installing pip dependencies with `/opt/hostedtoolcache/Python/3.12.8/x64/bin/python -m pip install yaml2bib rsync-time-machine slurm-usage pyyaml aiokef markdown-code-runner numthreads unidep`
+📦 Installing pip dependencies with `/opt/hostedtoolcache/Python/3.13.1/x64/bin/python -m pip install yaml2bib rsync-time-machine slurm-usage pyyaml aiokef markdown-code-runner numthreads unidep`
 
 📝 Found local dependencies: {'setup_py_project': ['hatch_project', 'setuptools_project']}
 
-📦 Installing project with `/opt/hostedtoolcache/Python/3.12.8/x64/bin/python -m pip install --no-deps -e /home/runner/work/unidep/unidep/example/hatch_project -e /home/runner/work/unidep/unidep/example/setuptools_project -e ./setup_py_project`
+📦 Installing project with `/opt/hostedtoolcache/Python/3.13.1/x64/bin/python -m pip install --no-deps -e /home/runner/work/unidep/unidep/example/hatch_project -e /home/runner/work/unidep/unidep/example/setuptools_project -e ./setup_py_project`
 
 ```
 
@@ -157,11 +157,11 @@ unidep install-all -e
 $ unidep install-all -e --dry-run
 📦 Installing conda dependencies with `conda install --yes --override-channels --channel conda-forge adaptive-scheduler numpy">=1.21" hpc05 pandas">=1,<3" pexpect adaptive">=0.15.0, <2.0.0" pfapack packaging pytest pytest-cov`
 
-📦 Installing pip dependencies with `/opt/hostedtoolcache/Python/3.12.8/x64/bin/python -m pip install unidep markdown-code-runner numthreads yaml2bib rsync-time-machine slurm-usage pyyaml aiokef`
+📦 Installing pip dependencies with `/opt/hostedtoolcache/Python/3.13.1/x64/bin/python -m pip install unidep markdown-code-runner numthreads yaml2bib rsync-time-machine slurm-usage pyyaml aiokef`
 
 📝 Found local dependencies: {'pyproject_toml_project': ['hatch_project'], 'setup_py_project': ['hatch_project', 'setuptools_project'], 'setuptools_project': ['hatch_project']}
 
-📦 Installing project with `/opt/hostedtoolcache/Python/3.12.8/x64/bin/python -m pip install --no-deps -e ./hatch2_project -e ./hatch_project -e ./pyproject_toml_project -e ./setup_py_project -e ./setuptools_project`
+📦 Installing project with `/opt/hostedtoolcache/Python/3.13.1/x64/bin/python -m pip install --no-deps -e ./hatch2_project -e ./hatch_project -e ./pyproject_toml_project -e ./setup_py_project -e ./setuptools_project`
 
 ```
 
diff --git a/tests/test_version_conflicts.py b/tests/test_version_conflicts.py
@@ -60,7 +60,7 @@ def test_is_valid_pinning(operator: str, version: str) -> None:
         ([">0.0.1", "<2", "=1.0.0"], "=1.0.0"),
         ([">1", "<=3", "<4"], ">1,<=3"),
         ([">1", "<=3"], ">1,<=3"),
-        # TODO #67: !=5 should be removed but this is not yet implemented  # noqa: TD004, FIX002, TD003
+        # TODO #67: !=5 should be removed but this is not yet implemented  # noqa: TD004, FIX002
         # However, this is not a problem here because !=5 is redundant
         # as it is outside the range of >1 and <=3
         ([">1", "<=3", "!=5"], ">1,<=3,!=5"),
