Merge branch 'main' into chore/use-prek

Author: d-v-b

.github/workflows/check_changelogs.yml

@@ -9,7 +9,7 @@ jobs:
     runs-on: ubuntu-latest
 
     steps:
-      - uses: actions/checkout@1af3b93b6815bc44a9784bd300feb67ff0d1eeb3 # v6.0.0
+      - uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
 
       - name: Install uv
         uses: astral-sh/setup-uv@61cb8a9741eeb8a550a1b8544337180c0fc8476b # v7.2.0

.github/workflows/codspeed.yml

@@ -17,7 +17,7 @@ jobs:
     name: Run benchmarks
     runs-on: codspeed-macro
     steps:
-    - uses: actions/checkout@v5
+    - uses: actions/checkout@v6
       with:
         fetch-depth: 0  # grab all branches and tags
     - name: Set up Python

changes/3656.misc.md

@@ -0,0 +1 @@
+Removed *rich* and *mypy* from the `[test]` dependencies, and added a new `[dev]` dependency group that can be used to install all the development dependencies.

docs/contributing.md

@@ -167,7 +167,7 @@ Zarr strives to maintain 100% test coverage under the latest Python stable relea
 hatch env run --env test.py3.12-2.2-optional run-coverage
 ```
 
-will automatically run the test suite with coverage and produce a XML coverage report. This should be 100% before code can be accepted into the main code base.
+will automatically run the test suite with coverage and produce an XML coverage report. This should be 100% before code can be accepted into the main code base.
 
 You can also generate an HTML coverage report by running:
 
@@ -297,4 +297,4 @@ performance benchmarks as part of our test suite. The benchmarks can be are foun
 By default pytest is configured to run these benchmarks as plain tests (i.e., no benchmarking). To run
 a benchmark with timing measurements, use the `--benchmark-enable` when invoking `pytest`.
 
-The benchmarks are run as part of the continuous integration suite through [codspeed](https://codspeed.io/zarr-developers/zarr-python).
+The benchmarks are run as part of the continuous integration suite through [codspeed](https://codspeed.io/zarr-developers/zarr-python).

docs/user-guide/storage.md

@@ -138,7 +138,7 @@ print(group)
 ```
 
 The type of filesystem (e.g. S3, https, etc..) is inferred from the scheme of the url (e.g. s3 for "**s3**://noaa-nwm-retro-v2-zarr-pds").
-In case a specific filesystem is needed, one can explicitly create it. For example to create a S3 filesystem:
+In case a specific filesystem is needed, one can explicitly create it. For example to create an S3 filesystem:
 
 ```python exec="true" session="storage" source="above" result="ansi"
 # Note: requires s3fs to be installed

pyproject.toml

@@ -70,15 +70,13 @@ gpu = [
     "cupy-cuda12x",
 ]
 cli = ["typer"]
-# Development extras
+# Testing extras
 test = [
     "coverage>=7.10",
     "pytest",
     "pytest-asyncio",
     "pytest-cov",
     "pytest-accept",
-    "rich",
-    "mypy",
     'numpydoc',
     "hypothesis",
     "pytest-xdist",
@@ -116,6 +114,14 @@ docs = [
     'astroid<4',
     'pytest'
 ]
+# All development extras
+dev = [
+    "zarr[optional]",
+    "zarr[test]",
+    "zarr[remote_tests]",
+    "zarr[docs]",
+    "mypy",
+]
 
 [project.scripts]
 zarr = "zarr._cli.cli:app"

src/zarr/core/dtype/wrapper.py

@@ -191,7 +191,7 @@ def to_json(self, zarr_format: ZarrFormat) -> DTypeSpec_V2 | DTypeSpec_V3:
     @abstractmethod
     def _check_scalar(self, data: object) -> bool:
         """
-        Check that an python object is a valid scalar value for the wrapped data type.
+        Check that a python object is a valid scalar value for the wrapped data type.
 
         Parameters
         ----------