- Update contribution guidelines.

- Added default python version for pre-commit.
- Don't test python 3.8 in mac and windows.

.github/workflows/tests.yaml

@@ -58,7 +58,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python: [3.8, 3.9, "3.10", 3.11, 3.12, 3.13]
+        python: [3.9, "3.10", 3.11, 3.12, 3.13]
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5
@@ -73,7 +73,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        python: [3.8, "3.10", 3.12]
+        python: ["3.10", 3.12]
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5

.pre-commit-config.yaml

@@ -1,5 +1,7 @@
 fail_fast: true
 default_install_hook_types: [pre-commit, pre-push]
+default_language_version:
+  python: python3.12
 
 ci:
   skip:
@@ -29,7 +31,7 @@ repos:
   - id: black
 
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: v0.9.6
+  rev: v0.9.9
   hooks:
   - id: ruff
     args: ["--fix"]
@@ -40,7 +42,7 @@ repos:
   - id: yesqa
 
 - repo: https://github.com/crate-ci/typos
-  rev: v1.29.5
+  rev: v1.30.1
   hooks:
   - id: typos
     args: []

CONTRIBUTING.rst

@@ -59,14 +59,18 @@ is done as follows:
 
 .. note::
 
-    The ``.pre-commit-config.yaml`` file was changed such that some hooks are
-    now run on ``pre-push``. If you have an old development environment, please
-    run ``pre-commit install`` again to update the git hooks.
+    ``.pre-commit-config.yaml`` is configured to run the hooks using python
+    3.12. Thus, you need to have python 3.12 installed for pre-commit to work.
 
 The ``pre-push`` stage runs several hooks (tests, doctests, mypy, coverage) that
-take some time. These are intended to let developers know problems which must be
-resolved for any pull request to be considered for merging. If you wish to push
-without running these hooks, use the command ``git push --no-verify``.
+take some time. These hooks are intended to inform developers of issues that
+must be resolved before any pull request can be considered for merging. If you
+wish to push without running these hooks, use the command ``git push
+--no-verify``.
+
+Formatting of the code is done automatically by pre-commit. If some pre-commit
+hooks fail and you decide to skip them, the formatting will be automatically
+applied by a github action in pull requests.
 
 Documentation
 -------------
@@ -86,7 +90,8 @@ Tests
 Running the unit tests can be done either using using `pytest
 <https://docs.pytest.org/>`__ or `tox
 <https://tox.readthedocs.io/en/stable/>`__. The tests are also installed with
-the package, thus can be run in a production system.
+the package, thus can be run in a production system. Also pre-commit runs some
+additional tests.
 
 .. code-block:: bash
 
@@ -96,6 +101,9 @@ the package, thus can be run in a production system.
     python -m jsonargparse_tests             # Run tests on installed package (requires pytest and pytest-subtests)
     pre-commit run -a --hook-stage pre-push  # Run pre-push git hooks (tests, doctests, mypy, coverage)
 
+Coverage
+--------
+
 For a nice html test coverage report, run:
 
 .. code-block:: bash