hvplot 0.12.1__tar.gz → 0.12.2__tar.gz

{hvplot-0.12.1 → hvplot-0.12.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: hvplot
-Version: 0.12.1
+Version: 0.12.2
 Summary: A high-level plotting API for the PyData ecosystem built on HoloViews.
 Project-URL: Homepage, https://hvplot.holoviz.org
 Project-URL: Source, http://github.com/holoviz/hvplot
@@ -19,6 +19,7 @@ Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Scientific/Engineering
 Classifier: Topic :: Software Development :: Libraries
 Requires-Python: >=3.10
@@ -33,8 +34,8 @@ Requires-Dist: param<3.0,>=1.12.0
 Provides-Extra: dev-extras
 Requires-Dist: setuptools-scm>=6; extra == 'dev-extras'
 Provides-Extra: doc
-Requires-Dist: bokeh-sampledata; (python_version >= '3.10') and extra == 'doc'
-Requires-Dist: dask[dataframe]<2025.1.0,>=2021.3.0; extra == 'doc'
+Requires-Dist: bokeh-sampledata>=2025.0; extra == 'doc'
+Requires-Dist: dask[dataframe]>=2021.3.0; extra == 'doc'
 Requires-Dist: datashader>=0.6.5; extra == 'doc'
 Requires-Dist: duckdb; extra == 'doc'
 Requires-Dist: fugue-sql-antlr>=0.2.0; extra == 'doc'
@@ -70,8 +71,8 @@ Requires-Dist: streamz>=0.3.0; extra == 'doc'
 Requires-Dist: xarray>=0.18.2; extra == 'doc'
 Requires-Dist: xyzservices>=2022.9.0; extra == 'doc'
 Provides-Extra: examples
-Requires-Dist: bokeh-sampledata; (python_version >= '3.10') and extra == 'examples'
-Requires-Dist: dask[dataframe]<2025.1.0,>=2021.3.0; extra == 'examples'
+Requires-Dist: bokeh-sampledata>=2025.0; extra == 'examples'
+Requires-Dist: dask[dataframe]>=2021.3.0; extra == 'examples'
 Requires-Dist: datashader>=0.6.5; extra == 'examples'
 Requires-Dist: duckdb; extra == 'examples'
 Requires-Dist: fugue-sql-antlr>=0.2.0; extra == 'examples'
@@ -103,8 +104,8 @@ Requires-Dist: streamz>=0.3.0; extra == 'examples'
 Requires-Dist: xarray>=0.18.2; extra == 'examples'
 Requires-Dist: xyzservices>=2022.9.0; extra == 'examples'
 Provides-Extra: examples-tests
-Requires-Dist: bokeh-sampledata; (python_version >= '3.10') and extra == 'examples-tests'
-Requires-Dist: dask[dataframe]<2025.1.0,>=2021.3.0; extra == 'examples-tests'
+Requires-Dist: bokeh-sampledata>=2025.0; extra == 'examples-tests'
+Requires-Dist: dask[dataframe]>=2021.3.0; extra == 'examples-tests'
 Requires-Dist: datashader>=0.6.5; extra == 'examples-tests'
 Requires-Dist: duckdb; extra == 'examples-tests'
 Requires-Dist: fugue-sql-antlr>=0.2.0; extra == 'examples-tests'
@@ -163,10 +164,10 @@ Requires-Dist: pyviz-comms>=0.0.1a1; extra == 'hvdev'
 Provides-Extra: hvdev-geo
 Requires-Dist: geoviews>=0.0.1a1; extra == 'hvdev-geo'
 Provides-Extra: tests
-Requires-Dist: bokeh-sampledata; (python_version >= '3.10') and extra == 'tests'
+Requires-Dist: bokeh-sampledata; extra == 'tests'
 Requires-Dist: cftime; extra == 'tests'
 Requires-Dist: dask; extra == 'tests'
-Requires-Dist: dask[dataframe]<2025.1.0; extra == 'tests'
+Requires-Dist: dask[dataframe]; extra == 'tests'
 Requires-Dist: duckdb; extra == 'tests'
 Requires-Dist: fugue-sql-antlr>=0.2.0; extra == 'tests'
 Requires-Dist: fugue[sql]; extra == 'tests'
@@ -190,9 +191,9 @@ Requires-Dist: spatialpandas; extra == 'tests'
 Requires-Dist: sqlglot; extra == 'tests'
 Requires-Dist: xarray; extra == 'tests'
 Provides-Extra: tests-core
-Requires-Dist: bokeh-sampledata; (python_version >= '3.10') and extra == 'tests-core'
+Requires-Dist: bokeh-sampledata; extra == 'tests-core'
 Requires-Dist: cftime; extra == 'tests-core'
-Requires-Dist: dask[dataframe]<2025.1.0; extra == 'tests-core'
+Requires-Dist: dask[dataframe]; extra == 'tests-core'
 Requires-Dist: ipywidgets; extra == 'tests-core'
 Requires-Dist: matplotlib; extra == 'tests-core'
 Requires-Dist: numpydoc; extra == 'tests-core'

{hvplot-0.12.1 → hvplot-0.12.2}/doc/conf.py

@@ -280,7 +280,7 @@ autosummary_generate = True
 # autosummary_generate_overwrite = False
 
 intersphinx_mapping = {
-    'cartopy': ('https://scitools.org.uk/cartopy/docs/latest/', None),
+    'cartopy': ('https://cartopy.readthedocs.io/stable/', None),
     'holoviews': ('https://holoviews.org/', None),
     'pandas': (
         'https://pandas.pydata.org/pandas-docs/stable/',

hvplot-0.12.2/doc/conftest.py

@@ -0,0 +1,146 @@
+import os
+import sys
+
+from importlib.util import find_spec
+
+import dask
+
+from packaging.version import Version, parse
+from bokeh.io.webdriver import webdriver_control
+from hvplot.util import _PD_GE_3_0_0
+
+# Examples that are slow to run and/or download large files.
+SLOW_EXAMPLES = [
+    'gallery/geospatial/datashade_map.ipynb',
+]
+
+collect_ignore_glob = [
+    'user_guide/Streaming.ipynb',
+]
+
+# Slow examples are excluded by default.
+if os.getenv('HVPLOT_INCLUDE_SLOW_EXAMPLES'):
+    collect_ignore_glob.extend(SLOW_EXAMPLES)
+
+
+if not find_spec('geoviews'):  # geo examples
+    collect_ignore_glob += [
+        'tutorials/getting_started.ipynb',
+        'gallery/geospatial/*.ipynb',
+        'gallery/gridded/rgb_satellite_imagery.ipynb',
+        'ref/api/manual/hvplot.hvPlot.paths.ipynb',
+        'ref/api/manual/hvplot.hvPlot.points.ipynb',
+        'ref/api/manual/hvplot.hvPlot.polygons.ipynb',
+        'ref/api/manual/hvplot.hvPlot.quadmesh.ipynb',
+        'ref/api/manual/hvplot.hvPlot.rgb.ipynb',
+        'ref/api/manual/hvplot.hvPlot.vectorfield.ipynb',
+        'ref/data_libraries.ipynb',
+        'ref/plotting_options/geographic.ipynb',
+        'user_guide/Explorer.ipynb',
+        'user_guide/Geographic_Data.ipynb',
+        'user_guide/Integrations.ipynb',
+    ]
+
+if not find_spec('datashader'):
+    collect_ignore_glob += [
+        'ref/api/manual/hvplot.plotting.scatter_matrix.ipynb',
+        'ref/plotting_options/resampling.ipynb',
+        'user_guide/Gridded_Data.ipynb',
+        'user_guide/Large_Timeseries.ipynb',
+        'user_guide/Plotting.ipynb',
+        'user_guide/Plotting_with_Matplotlib.ipynb',
+        'user_guide/Plotting_with_Plotly.ipynb',
+    ]
+
+if not find_spec('streamz') or sys.version_info[:2] >= (3, 14):
+    collect_ignore_glob += [
+        'ref/plotting_options/streaming.ipynb',
+    ]
+
+if _PD_GE_3_0_0:
+    # Because of fugue
+    collect_ignore_glob += ['ref/data_libraries.ipynb']
+
+try:
+    import ibis
+    import duckdb
+
+    # 'Ibis <= 10.8.0 is incompatible with DuckDB >= 1.4')
+    if parse(ibis.__version__) <= parse('10.8.0') and parse(duckdb.__version__) >= parse('1.4'):
+        collect_ignore_glob += ['ref/data_libraries.ipynb']
+except ImportError:
+    pass
+
+if find_spec('selenium'):
+    try:
+        webdriver_control.create()
+    except RuntimeError:
+        # hvplot.save() with bokeh
+        collect_ignore_glob += [
+            'user_guide/Viewing.ipynb',
+            'user_guide/NetworkX.ipynb',
+        ]
+    finally:
+        webdriver_control.cleanup()
+
+pygraphviz = None
+
+try:
+    import pygraphviz  # noqa
+except ImportError:
+    pass
+
+pydot = None
+try:
+    import pydot  # noqa
+except ImportError:
+    pass
+
+if pygraphviz is None and pydot is None:
+    collect_ignore_glob += ['user_guide/NetworkX.ipynb']
+
+if Version(dask.__version__).release < (2025, 1, 0):
+    # From Dask 2024.3.0 they now use `dask_expr` by default
+    # https://github.com/dask/dask/issues/10995
+    dask.config.set({'dataframe.query-planning': False})
+
+
+# https://github.com/pydata/xarray/pull/9182
+try:
+    import xarray as xr
+except ImportError:
+    pass
+else:
+    import numpy as np
+
+    if Version(np.__version__) >= Version('2.0.0') and Version(xr.__version__) <= Version(
+        '2024.6.0'
+    ):
+        collect_ignore_glob += [
+            'user_guide/Gridded_Data.ipynb',
+        ]
+
+
+def pytest_runtest_makereport(item, call):
+    """
+    Skip tests that fail because "the kernel died before replying to kernel_info"
+    this is a common error when running the example tests in CI.
+
+    Inspired from: https://stackoverflow.com/questions/32451811
+
+    """
+    from _pytest.runner import pytest_runtest_makereport
+
+    tr = pytest_runtest_makereport(item, call)
+
+    if call.excinfo is not None:
+        msgs = [
+            'Kernel died before replying to kernel_info',
+            "Kernel didn't respond in 60 seconds",
+        ]
+        for msg in msgs:
+            if call.excinfo.type is RuntimeError and call.excinfo.value.args[0] in msg:
+                tr.outcome = 'skipped'
+                tr.wasxfail = f'reason: {msg}'
+
+    return tr

{hvplot-0.12.1 → hvplot-0.12.2}/doc/ref/plotting_options/axis.ipynb

@@ -881,7 +881,9 @@
     "(option-xlim_ylim)=\n",
     "## `xlim / ylim`\n",
     "\n",
-    "The x- and y-axis ranges can be defined with the `xlim` and `ylim` options, respectively. These options accept a 2-tuple representing the minimum and maximum bounds of the plotted ranged. One bound can be left unset by using `None` (e.g. `xlim=(10, None)` means there is no upper bound)."
+    "The x- and y-axis ranges can be defined with the `xlim` and `ylim` options, respectively. These options accept a 2-tuple representing the minimum and maximum bounds of the plotted ranged. One bound can be left unset by using `None` (e.g. `xlim=(10, None)` means there is no upper bound).\n",
+    "\n",
+    "If [`tiles`](option-tiles) is provided and the `xlim` and `ylim` are in `lat`/`lon` coordinates, they will be automatically transformed to Web Mercator coordinates."
    ]
   },
   {

{hvplot-0.12.1 → hvplot-0.12.2}/doc/ref/plotting_options/color_colormap.ipynb

@@ -54,8 +54,8 @@
     "The `color` option sets the color of the plotted elements. It accepts:\n",
     "\n",
     "- A single color name or hex code (e.g., `'red'`, `'#1f77b4'`) to apply uniformly.\n",
-    "- A list of colors to cycle through when plotting multiple groups (e.g., with `by='column'`).\n",
     "- A column name to map colors based on data values (for categorical or continuous color encoding).\n",
+    "- A list of colors to cycle through when plotting multiple groups (e.g., with `by='column'`).\n",
     "- A column containing per-point color values (e.g., hex codes).\n",
     "\n",
     "If both `color` and `c` are provided, `color` takes precedence. For categorical data, hvPlot automatically uses a discrete colormap unless overridden."
@@ -71,11 +71,6 @@
     "import hvplot.pandas  # noqa\n",
     "\n",
     "df = hvplot.sampledata.penguins(\"pandas\")\n",
-    "df['custom_color'] = df['species'].map({\n",
-    "    'Adelie': 'red',\n",
-    "    'Gentoo': 'purple',\n",
-    "    'Chinstrap': 'grey',\n",
-    "})\n",
     "\n",
     "plot_opts = dict(x=\"flipper_length_mm\", y=\"body_mass_g\", frame_width=250)\n",
     "(\n",
@@ -83,14 +78,15 @@
     "        color=\"#d133ff\", title=\"Colored by single hex color\", **plot_opts\n",
     "    ) +\n",
     "    df.hvplot.scatter(\n",
-    "        by=\"species\", color=[\"blue\", \"green\", \"orange\"],\n",
-    "        title=\"Groups colored by custom list\", **plot_opts\n",
+    "        color=\"species\", title=\"Colored by column name\", **plot_opts\n",
     "    ) +\n",
     "    df.hvplot.scatter(\n",
-    "        color=\"species\", title=\"Colored by column name\", **plot_opts\n",
+    "        by=\"species\", color=[\"blue\", \"green\", \"orange\"],\n",
+    "        title=\"Groups colored by custom list\", **plot_opts\n",
     "    ) +\n",
     "    df.hvplot.scatter(\n",
-    "        color=\"custom_color\", title=\"Colored by mapped color column\", **plot_opts\n",
+    "        color=df['species'].map({'Adelie': 'red', 'Gentoo': 'purple', 'Chinstrap': 'grey'}),\n",
+    "        title=\"Per-point color value\", **plot_opts,\n",
     "    )\n",
     ").cols(2)"
    ]
@@ -130,6 +126,35 @@
     ":::"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "id": "be669a46",
+   "metadata": {},
+   "source": [
+    "::: {tip} Categorical Custom Color Mapping: Best Practice\n",
+    "\n",
+    "When you want to map categorical values to specific colors, use `color='column_name'` with `cmap={...}` instead of passing a pre-mapped Series:\n",
+    "\n",
+    "**✅ Recommended:**\n",
+    "```python\n",
+    "df.hvplot.scatter(\n",
+    "    x='x', y='y', color='species',\n",
+    "    cmap={'Adelie': 'blue', 'Gentoo': 'yellow', 'Chinstrap': 'red'}\n",
+    ")\n",
+    "```\n",
+    "\n",
+    "**❌ Not recommended:**\n",
+    "```python\n",
+    "df.hvplot.scatter(\n",
+    "    x='x', y='y',\n",
+    "    color=df['species'].map({'Adelie': 'blue', ...})\n",
+    ")\n",
+    "```\n",
+    "\n",
+    "Using `color='column_name'` with `cmap` keeps your original data visible in hover tooltips and provides a cleaner, more maintainable API.\n",
+    ":::"
+   ]
+  },
   {
    "cell_type": "markdown",
    "id": "7a03fc23-d338-44df-9777-9f06ad1096eb",
@@ -170,25 +195,25 @@
     "\n",
     "df = hvplot.sampledata.earthquakes(\"pandas\")\n",
     "\n",
-    "plot_opts = dict(x=\"lon\", y=\"lat\", color=\"mag\", frame_width=250)\n",
+    "plot_opts = dict(x=\"lon\", y=\"lat\", frame_width=250)\n",
     "plot1 = df.hvplot.scatter(\n",
-    "    cmap=\"plasma_r\", title=\"Named cmap 'plasma_r'\", **plot_opts\n",
+    "    cmap=\"plasma_r\", title=\"Named cmap 'plasma_r'\", color=\"mag\", **plot_opts\n",
     ")\n",
     "plot2 = df.hvplot.scatter(\n",
     "    cmap=[\n",
     "        '#f7fbff', '#deebf7', '#c6dbef', '#9ecae1',\n",
     "        '#6baed6', '#4292c6', '#2171b5', '#084594',\n",
-    "    ], title=\"Custom list cmap\", **plot_opts\n",
+    "    ], title=\"Custom list cmap\", color=\"mag\", **plot_opts\n",
     ")\n",
     "plot3 = df.hvplot.scatter(\n",
-    "    cmap=mpl.colormaps[\"OrRd\"], title=\"MPL colormap object 'OrRd'\", **plot_opts\n",
+    "    cmap=mpl.colormaps[\"OrRd\"], title=\"MPL colormap object 'OrRd'\", color=\"mag\", **plot_opts\n",
     ")\n",
     "plot4 = df.hvplot.scatter(\n",
     "    cmap={\n",
     "        'Shallow': 'orange',\n",
     "        'Intermediate': '#C70039',\n",
     "        'Deep': '#581845',\n",
-    "    }, title=\"Dict keys categorical cmap\", **{**plot_opts, **{\"color\": \"depth_class\"}},\n",
+    "    }, title=\"Dict keys categorical cmap\", color=\"depth_class\", **plot_opts,\n",
     ")\n",
     "(plot1 + plot2 + plot3 + plot4).cols(2)"
    ]

{hvplot-0.12.1 → hvplot-0.12.2}/doc/ref/plotting_options/data.ipynb

@@ -13,6 +13,55 @@
     "```"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "metadata": {},
+   "source": [
+    "(option-attr_labels)=\n",
+    "## `attr_labels`\n",
+    "\n",
+    "The `attr_labels` option controls whether hvPlot automatically uses xarray object attributes as labels for dimensions in your plots. This feature helps create more descriptive plots by extracting meaningful labels and units from your xarray data's metadata.\n",
+    "\n",
+    "When set to `True`, hvPlot will look for `long_name` attributes to use as dimension labels and `units` attributes to add unit information. If set to `None` (the default), hvPlot attempts to extract labels without showing warnings if attributes aren't found. Setting it to `False` disables this automatic labeling behavior entirely.\n",
+    "\n",
+    ":::{note}\n",
+    "This option only applies to xarray data objects that contain attributes. It has no effect on pandas DataFrames or other data types.\n",
+    ":::"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import hvplot.xarray # noqa\n",
+    "\n",
+    "ds = hvplot.sampledata.air_temperature(\"xarray\").sel(time='2014-02-25 12:00')\n",
+    "print(\"Longitude coordinates:\", ds.coords['lon'].attrs)\n",
+    "print(\"Latitude coordinates:\", ds.coords['lat'].attrs)"
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "plot1 = ds.hvplot.image(\n",
+    "    title=\"attr_labels=None (default)\",\n",
+    "    width=350, height=250,\n",
+    ")\n",
+    "\n",
+    "plot2 = ds.hvplot.image(\n",
+    "    attr_labels=False,\n",
+    "    title=\"attr_labels=False\",\n",
+    "    width=350, height=250\n",
+    ")\n",
+    "\n",
+    "plot1 + plot2"
+   ]
+  },
   {
    "cell_type": "markdown",
    "metadata": {},

{hvplot-0.12.1 → hvplot-0.12.2}/doc/ref/plotting_options/geographic.ipynb

@@ -425,6 +425,37 @@
     "layout.cols(2)"
    ]
   },
+  {
+   "cell_type": "markdown",
+   "id": "dcc48e78",
+   "metadata": {},
+   "source": [
+    "If `xlim` and `ylim` are in `lat`/`lon` coordinates, they will be automatically transformed to Web Mercator coordinates."
+   ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "id": "0f86e368",
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "import holoviews as hv\n",
+    "import hvplot.pandas  # noqa\n",
+    "import xyzservices.providers as xyz\n",
+    "\n",
+    "df = hvplot.sampledata.earthquakes(\"pandas\")\n",
+    "\n",
+    "plot_opts = dict(x='lon', y='lat', alpha=0.2, c='brown', frame_width=250, xlim=(-130, -70), ylim=(30, 60))\n",
+    "layout = (\n",
+    "    df.hvplot.points(tiles=True, title=\"Default: OpenStreetMap\", **plot_opts) +\n",
+    "    df.hvplot.points(tiles=xyz.Esri.WorldPhysical, title=\"xyz.Esri.WorldPhysical\", **plot_opts) +\n",
+    "    df.hvplot.points(tiles='EsriTerrain', title=\"EsriTerrain string\", **plot_opts) +\n",
+    "    df.hvplot.points(tiles=hv.element.tiles.EsriImagery, title=\"HoloViews Tiles\", **plot_opts)\n",
+    ")\n",
+    "layout.cols(2)"
+   ]
+  },
   {
    "cell_type": "markdown",
    "id": "d0db0527-bb56-4e99-8864-22819b6367c3",

{hvplot-0.12.1 → hvplot-0.12.2}/doc/releases.md

@@ -2,6 +2,41 @@
 
 See [the HoloViz blog](https://blog.holoviz.org/#category=hvplot) for a visual summary of the major features added in a selection of releases.
 
+## Version 0.12.2 (2025-12-18)
+
+The 0.12.2 release is a patch release that brings a few bugfixes and enhancements. Many thanks to @ahuang11, @Azaya89, @hoxbro, @MarcSkovMadsen, @maximlt, and @MridulS for their contributions!
+
+Enhancements:
+
+- Automatically convert `xlim/ylim` to Web Mercator when `tiles=True` ([#1685](https://github.com/holoviz/hvplot/pull/1685))
+- Automatically use `y` as default `text` kwarg if only two columns ([#1681](https://github.com/holoviz/hvplot/pull/1681))
+
+Bug Fixes:
+
+- Fix handling of `hv.dim` expressions in `size` and `color` parameters ([#1691](https://github.com/holoviz/hvplot/pull/1691))
+- Exclude internal style columns (`_color` and `_size`) from tooltips ([#1690](https://github.com/holoviz/hvplot/pull/1690))
+
+Documentation:
+
+- Document `attr_labels` ([#1677](https://github.com/holoviz/hvplot/pull/1677))
+- Fix typo in the NetworkX user guide ([#1686](https://github.com/holoviz/hvplot/pull/1686))
+- Scale networkx layout and fix graphviz init in doc build ([#1672](https://github.com/holoviz/hvplot/pull/1672))
+- Roadmap updates ([#1694](https://github.com/holoviz/hvplot/pull/1694))
+
+Compatibility:
+
+- Ensure Python 3.14 support ([#1688](https://github.com/holoviz/hvplot/pull/1688), [#1703](https://github.com/holoviz/hvplot/pull/1703))
+- Compatibility with the latest versions of DuckDB ([#1682](https://github.com/holoviz/hvplot/pull/1682))
+- Compatibility with the upcoming Pandas 3.0 ([#1704](https://github.com/holoviz/hvplot/pull/1704))
+
+Infrastructure / Tests:
+
+- Address warnings emitted by the unit tests suite ([#1700](https://github.com/holoviz/hvplot/pull/1700))
+- Miscellaneous changes ([#1697](https://github.com/holoviz/hvplot/pull/1697), [#1698](https://github.com/holoviz/hvplot/pull/1698), [#1699](https://github.com/holoviz/hvplot/pull/1699), [#1701](https://github.com/holoviz/hvplot/pull/1701), [#1702](https://github.com/holoviz/hvplot/pull/1702), [#1706](https://github.com/holoviz/hvplot/pull/1706), [#1707](https://github.com/holoviz/hvplot/pull/1707))
+
+[Full Changelog](https://github.com/holoviz/hvplot/compare/v0.12.1...v0.12.2)
+
+
 ## Version 0.12.1 (2025-08-29)
 
 The 0.12.1 release is a patch release that brings a few bugfixes and enhancements, and most importantly adds a new extended [Gallery](https://hvplot.holoviz.org/en/docs/latest/gallery/index.html) top-level section with about 50 examples, replacing the previous and limited *Reference Gallery*. Many thanks to @kmnhan (first contribution!), @hoxbro, @Azaya89, and @maximlt for their contributions!

hvplot-0.12.2/doc/roadmap.md

@@ -0,0 +1,70 @@
+# Roadmap
+
+hvPlot was released in 2018 and has gained many features since then, becoming a super-charged version of Pandas `.plot()` API, with support for many data structures of the PyData ecosystem (Pandas, Dask, Xarray, GeoPandas, etc.), for multiple plotting backends, and for many powerful features (plotting large datasets with Datashader, geographic data with GeoViews, plotting streaming data, etc.). Despite this, hvPlot isn't currently as widely known as some of the alternatives and has huge room to grow.
+
+## hvPlot development principles
+
+The following principles are derived from the goal of improving hvPlot's stability and user-friendliness.
+
+1. Reliability first
+
+Prioritize reducing bugs over introducing new features. New features and enhancements are welcome, but only when they do not compromise overall stability. Bugs originating in hvPlot's dependencies, particularly HoloViews, should be easy for users to discover, track, and see resolved through clear GitHub issues and coordinated fixes.
+
+2. Documentation as a core feature
+
+Treat documentation as a first-class part of the project. Continuously improve clarity, coverage, and examples, such as by expanding the gallery, until the documentation meets or exceeds the quality of comparable libraries (e.g. Altair, Plotly Express, plotnine). Ensure documentation remains accurate and up to date as the codebase evolves.
+
+3. Strong, accessible testing
+
+Maintain a test suite that meaningfully catches regressions and common user errors. Make writing and extending tests straightforward so that contributors can easily add coverage alongside bug fixes and new functionality.
+
+4. User-centered developer experience
+
+Improve the day-to-day experience of using hvPlot by adding type hints to support IDE tooling and by providing clearer, more actionable error messages when things go wrong.
+
+5. Deep integration with the PyData ecosystem
+
+Actively increase hvPlot’s visibility and adoption across the PyData ecosystem. Engage maintainers of related libraries through issues and discussions to explore deeper integration or exposure of hvPlot, and support those efforts with documentation updates and ongoing collaboration.
+
+6. Thoughtful feature completeness
+
+Expose stable, relevant HoloViews capabilities through hvPlot when they add clear user value (e.g. dual axes, native Polars support). Identify and implement essential plotting features expected of a general-purpose plotting library when they are missing (e.g. pie charts), while maintaining hvPlot's simplicity and reliability.
+
+Based on these principles, we aim to release 1.0 in early 2026, signaling to hvPlot's user base that it is a stable project already for a few years.
+
+## hvPlot 1.0
+
+### 1. Documentation
+
+In 2025, we obtained a Small Development Grant from NumFocus that allowed us to significantly update the documentation, adding a new Reference section with a description of all plotting options and an automated API reference, a new examples gallery, and new tutorials.
+
+To complete this documentation update, we now need to convert the user guides into How-To guides, Tutorials, and Explanation pages.
+
+### 2. Refactor the test suite
+
+The test suite should be refactored and improved to catch bugs before users have to report them and to prevent potential regressions.
+
+### 3. Add donut and pie charts
+
+There are many references in the literature that argue that pie charts do not communicate data precisely enough (humans judge length better than angle, so it’s difficult to compare slices accurately). For this reason, pie charts have not been added to HoloViews, which instead recommends bar charts. Yet pie charts are very commonly used, and not offering this option in hvPlot is a significant gap we aim to fill by adding a Donut plot type in HoloViews and `donut` and `pie` methods to hvPlot.
+
+### 4. Native support for more dataframe libraries like Polars
+
+HoloViews added support in version 1.22.0 for Narwhals as a data backend. Narwhals is a library that provides a unified interface to many DataFrame libraries (its API being heavily inspired by Polars). hvPlot already provides good support for various DataFrame libraries, like Pandas and Dask, when these libraries have a data backend implemented in HoloViews. When they do not — as was the case for Polars, for example — hvPlot previously cast the user's DataFrame to a supported type (usually Pandas). With HoloViews' Narwhals backend, hvPlot can now avoid upfront casting and pass DataFrames directly to HoloViews, which can handle them via Narwhals.
+
+## Post hvPlot 1.0
+
+### 1. Figure out the future of the `.interactive` API
+
+Param 2.0 introduced a new API for reactive expressions, allowing Param users and users of libraries leveraging this feature (like Panel) to write purely reactive code. Reactive expressions are, in fact, a generalized and improved re-implementation of `.interactive()` from hvPlot.
+
+1. hvPlot should determine whether the `.interactive()` API still has a place in the project.
+2. If so, its implementation should be updated to use Param's implementation. If not, the feature should be deprecated.
+
+## 2. Improve the Explorer
+
+The Explorer is still in development and needs improvements in several areas.
+
+1. The Explorer's design and user experience should draw inspiration from other similar components (e.g. Tableau, Excel, Superset).
+2. The Explorer should work well with all the data types supported by hvPlot.
+3. The Explorer should be better integrated into the documentation, both as a tool to explore hvPlot's API and to explore data.

{hvplot-0.12.1 → hvplot-0.12.2}/doc/user_guide/NetworkX.ipynb

@@ -32,7 +32,7 @@
    "source": [
     "In this user guide we will follow along with many of the examples in the [NetworkX tutorial](https://networkx.github.io/documentation/stable/tutorial.html#drawing-graphs) on drawing graphs.\n",
     "\n",
-    "The ``hxnx`` namespace provides all the same plotting functions as ``nx``, this means in most cases one can simply be swapped for the other. This also includes most keywords used to customize the plots. The main difference is in the way multiple plots are composited, like all other hvPlot APIs the networkX functions returns HoloViews objects which can be composited using ``+`` and ``*`` operations:"
+    "The ``hvnx`` namespace provides all the same plotting functions as ``nx``, this means in most cases one can simply be swapped for the other. This also includes most keywords used to customize the plots. The main difference is in the way multiple plots are composited, like all other hvPlot APIs the networkX functions returns HoloViews objects which can be composited using ``+`` and ``*`` operations:"
    ]
   },
   {
@@ -96,10 +96,11 @@
     "G = nx.dodecahedral_graph()\n",
     "\n",
     "shells = [[2, 3, 4, 5, 6], [8, 1, 0, 19, 18, 17, 16, 15, 14, 7], [9, 10, 11, 12, 13]]\n",
-    "shell = hvnx.draw_shell(G, nlist=shells)\n",
+    "shell_pos = nx.shell_layout(G, nlist=shells, scale=100)\n",
+    "shell = hvnx.draw(G, pos=shell_pos)\n",
     "\n",
-    "pos = nx.nx_agraph.graphviz_layout(G)\n",
-    "graphviz = hvnx.draw(G, pos=pos)\n",
+    "graphviz_pos = nx.nx_agraph.graphviz_layout(G)\n",
+    "graphviz = hvnx.draw(G, pos=graphviz_pos)\n",
     "\n",
     "layout = shell + graphviz\n",
     "layout"

{hvplot-0.12.1 → hvplot-0.12.2}/hvplot/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.12.1'
-__version_tuple__ = version_tuple = (0, 12, 1)
+__version__ = version = '0.12.2'
+__version_tuple__ = version_tuple = (0, 12, 2)
 
 __commit_id__ = commit_id = None