diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml index 0131ab47aa..a373f2cf75 100644 --- a/.pre-commit-config.yaml +++ b/.pre-commit-config.yaml @@ -5,7 +5,7 @@ exclude: (\.min\.js$|\.svg$|\.html$) default_stages: [commit] repos: - repo: https://github.com/pre-commit/pre-commit-hooks - rev: v4.4.0 + rev: v4.5.0 hooks: - id: check-builtin-literals - id: check-case-conflict @@ -17,17 +17,17 @@ repos: exclude: \.min\.js$ - id: trailing-whitespace - repo: https://github.com/astral-sh/ruff-pre-commit - rev: v0.0.291 + rev: v0.0.292 hooks: - id: ruff args: [holoviews] files: holoviews/ - repo: https://github.com/hoxbro/clean_notebook - rev: v0.1.11 + rev: v0.1.13 hooks: - id: clean-notebook - repo: https://github.com/codespell-project/codespell - rev: v2.2.5 + rev: v2.2.6 hooks: - id: codespell additional_dependencies: diff --git a/examples/user_guide/07-Live_Data.ipynb b/examples/user_guide/07-Live_Data.ipynb index 353380585f..8b3f9bb505 100644 --- a/examples/user_guide/07-Live_Data.ipynb +++ b/examples/user_guide/07-Live_Data.ipynb @@ -32,7 +32,7 @@ "* DynamicMaps store only a portion of the underlying data, in the form of an Element cache and their output is dependent on the particular version of the executed code. \n", "* DynamicMaps (and particularly their element caches) are typically stateful (with values that depend on patterns of user interaction), which can make them more difficult to reason about.\n", "\n", - "In addition to the different computational requirements of ``DynamicMaps``, they can be used to build sophisticated, interactive vizualisations that cannot be achieved using only ``HoloMaps``. This notebook demonstrates some basic examples and the [Responding to Events](./12-Responding_to_Events.ipynb) guide follows on by introducing the streams system. The [Custom Interactivity](./13-Custom_Interactivity.ipynb) shows how you can directly interact with your plots when using the Bokeh backend.\n", + "In addition to the different computational requirements of ``DynamicMaps``, they can be used to build sophisticated, interactive visualisations that cannot be achieved using only ``HoloMaps``. This notebook demonstrates some basic examples and the [Responding to Events](./12-Responding_to_Events.ipynb) guide follows on by introducing the streams system. The [Custom Interactivity](./13-Custom_Interactivity.ipynb) shows how you can directly interact with your plots when using the Bokeh backend.\n", "\n", "When DynamicMap was introduced in version 1.6, it supported multiple different 'modes' which have now been deprecated. This notebook demonstrates the simpler, more flexible and more powerful DynamicMap introduced in version 1.7. Users who have been using the previous version of DynamicMap should be unaffected as backwards compatibility has been preserved for the most common cases.\n", "\n", diff --git a/examples/user_guide/Notebook_Magics.ipynb b/examples/user_guide/Notebook_Magics.ipynb index e8624d0571..498922d8cf 100644 --- a/examples/user_guide/Notebook_Magics.ipynb +++ b/examples/user_guide/Notebook_Magics.ipynb @@ -52,7 +52,7 @@ "There are two types of magic supported in Jupyter notebooks called *line magics* and *cell magics* respectively. Both typically appear at the top of code cells prefixed by `%` (line magics) or `%%` (cell magics).\n", "\n", "* **line magics**: These can appear anywhere in a code cell and effect global changes to the current notebook session. HoloViews has the `%opts` and `%output` line magics.\n", - "* **cell magics**: These have to appear at the top of the cell and are used to modify how that cell is executed. HoloViews has the `%%opts` and `%%ouput` cell magics.\n", + "* **cell magics**: These have to appear at the top of the cell and are used to modify how that cell is executed. HoloViews has the `%%opts` and `%%output` cell magics.\n", "\n" ] }, diff --git a/holoviews/core/data/xarray.py b/holoviews/core/data/xarray.py index 3ac3bd51cf..629ec1cf24 100644 --- a/holoviews/core/data/xarray.py +++ b/holoviews/core/data/xarray.py @@ -604,7 +604,7 @@ def select(cls, dataset, selection_mask=None, **selection): if dropped and not indexed: data = data.expand_dims(dropped) # see https://github.com/pydata/xarray/issues/2891 - # since we only exapanded on dimnesions of size 1 + # since we only expanded on dimensions of size 1 # we can monkeypatch the dataarray back to writeable. for d in data.values(): if hasattr(d.data, 'flags'): diff --git a/holoviews/tests/plotting/plotly/test_dynamic.py b/holoviews/tests/plotting/plotly/test_dynamic.py index e53d001180..7f51afe675 100644 --- a/holoviews/tests/plotting/plotly/test_dynamic.py +++ b/holoviews/tests/plotting/plotly/test_dynamic.py @@ -135,7 +135,7 @@ def test_interactive_streams(self): self.assertEqual(boundsxy2a.bounds, (10, 11, 20, 22)) self.assertEqual(boundsxy2b.bounds, (10, 11, 20, 22)) - # Box selecrt on third subplot + # Box select on third subplot plotly_pane.selected_data = { 'points': [ {'curveNumber': 2, 'pointNumber': 0}, diff --git a/tox.ini b/tox.ini index d1d7da90c7..5d8ce959f2 100644 --- a/tox.ini +++ b/tox.ini @@ -13,17 +13,17 @@ commands = python -c "import holoviews as hv; print(hv.__version__)" [_unit_core] description = Run unit tests with coverage but no optional test dependency deps = .[tests_core] -commands = pytest holoviews --cov=./holoviews -v +commands = pytest holoviews --cov=./holoviews [_unit] description = Run unit tests with coverage and all the optional test dependencies deps = .[tests] -commands = pytest holoviews --cov=./holoviews -v +commands = pytest holoviews --cov=./holoviews [_unit_gpu] description = Run unit tests with coverage and all the optional test dependencies deps = .[tests_gpu] -commands = pytest holoviews --cov=./holoviews -v +commands = pytest holoviews --cov=./holoviews [_ui] description = Run UI tests