hvplot 0.9.1rc1__tar.gz → 0.9.2__tar.gz

{hvplot-0.9.1rc1/hvplot.egg-info → hvplot-0.9.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: hvplot
-Version: 0.9.1rc1
+Version: 0.9.2
 Summary: A high-level plotting API for the PyData ecosystem built on HoloViews.
 Home-page: https://hvplot.holoviz.org
 Author: Philipp Rudiger
@@ -171,6 +171,7 @@ Requires-Dist: polars; extra == "doc"
 Requires-Dist: fugue; extra == "doc"
 Requires-Dist: ibis-framework; extra == "doc"
 Requires-Dist: nbsite>=0.8.4; extra == "doc"
+Requires-Dist: sphinxext-rediraffe; extra == "doc"
 Provides-Extra: build
 Requires-Dist: param>=1.7.0; extra == "build"
 Requires-Dist: pyct>=0.4.4; extra == "build"
@@ -221,6 +222,7 @@ Requires-Dist: scipy>=1.5.3; extra == "all"
 Requires-Dist: selenium>=3.141.0; extra == "all"
 Requires-Dist: setuptools>=30.3.0; extra == "all"
 Requires-Dist: spatialpandas>=0.4.3; extra == "all"
+Requires-Dist: sphinxext-rediraffe; extra == "all"
 Requires-Dist: streamz>=0.3.0; extra == "all"
 Requires-Dist: xarray; extra == "all"
 Requires-Dist: xarray>=0.18.2; extra == "all"
@@ -250,7 +252,7 @@ The API is based on the familiar Pandas `.plot` API and the innovative `.interac
 
 hvPlot
 
-- supports a wide range of data sources including [Pandas](http://pandas.pydata.org), [XArray](http://xarray.pydata.org), [Dask](http://dask.pydata.org), [Streamz](http://streamz.readthedocs.io), [Intake](http://github.com/ContinuumIO/intake), [GeoPandas](http://geopandas.org) and [NetworkX](https://networkx.github.io/documentation/stable/).
+- supports a wide range of data sources including [Pandas](http://pandas.pydata.org), [Polars](https://docs.pola.rs/), [XArray](http://xarray.pydata.org), [Dask](http://dask.pydata.org), [Streamz](http://streamz.readthedocs.io), [Intake](http://github.com/ContinuumIO/intake), [GeoPandas](http://geopandas.org) and [NetworkX](https://networkx.github.io/documentation/stable/).
 - supports the plotting backends [Bokeh](https://docs.bokeh.org/en/latest/), [Matplotlib](https://matplotlib.org/) and [Plotly](https://plotly.com/python/).
 - exposes the powerful tools from the [HoloViz](https://holoviz.org/) ecosystem in a familiar and convenient API.
 
@@ -342,10 +344,6 @@ In a notebook or ipython environment the usual
 - `help` and `?` will provide you with documentation.
 - `TAB` and `SHIFT+TAB` completion will help you navigate.
 
-## Examples
-
-[<img src="http://blog.holoviz.org/images/hvplot_collage.png" style="max-height:400px;border-radius:2%;">](https://hvplot.holoviz.org/topics.html)
-
 ## License
 
 hvPlot is completely free and open-source. It is licensed under the [BSD 3-Clause License](https://opensource.org/licenses/BSD-3-Clause).

{hvplot-0.9.1rc1 → hvplot-0.9.2}/README.md

@@ -23,7 +23,7 @@ The API is based on the familiar Pandas `.plot` API and the innovative `.interac
 
 hvPlot
 
-- supports a wide range of data sources including [Pandas](http://pandas.pydata.org), [XArray](http://xarray.pydata.org), [Dask](http://dask.pydata.org), [Streamz](http://streamz.readthedocs.io), [Intake](http://github.com/ContinuumIO/intake), [GeoPandas](http://geopandas.org) and [NetworkX](https://networkx.github.io/documentation/stable/).
+- supports a wide range of data sources including [Pandas](http://pandas.pydata.org), [Polars](https://docs.pola.rs/), [XArray](http://xarray.pydata.org), [Dask](http://dask.pydata.org), [Streamz](http://streamz.readthedocs.io), [Intake](http://github.com/ContinuumIO/intake), [GeoPandas](http://geopandas.org) and [NetworkX](https://networkx.github.io/documentation/stable/).
 - supports the plotting backends [Bokeh](https://docs.bokeh.org/en/latest/), [Matplotlib](https://matplotlib.org/) and [Plotly](https://plotly.com/python/).
 - exposes the powerful tools from the [HoloViz](https://holoviz.org/) ecosystem in a familiar and convenient API.
 
@@ -115,10 +115,6 @@ In a notebook or ipython environment the usual
 - `help` and `?` will provide you with documentation.
 - `TAB` and `SHIFT+TAB` completion will help you navigate.
 
-## Examples
-
-[<img src="http://blog.holoviz.org/images/hvplot_collage.png" style="max-height:400px;border-radius:2%;">](https://hvplot.holoviz.org/topics.html)
-
 ## License
 
 hvPlot is completely free and open-source. It is licensed under the [BSD 3-Clause License](https://opensource.org/licenses/BSD-3-Clause).

{hvplot-0.9.1rc1/hvplot → hvplot-0.9.2}/examples/getting_started/interactive.ipynb

@@ -2,6 +2,7 @@
  "cells": [
   {
    "cell_type": "markdown",
+   "id": "66dddf49-c70a-4ed1-98e7-76703b82fa34",
    "metadata": {},
    "source": [
     "hvPlot isn't only a plotting library, it is dedicated to make data exploration easier. In this guide you will see how it can help you to get better control over your data pipelines. We define a *data pipeline* as a series of commands that *transform* some data, such as aggregating, filtering, reshaping, renaming, etc. A data pipeline may include a *load* step that will provide the input data to the pipeline, e.g. reading the data from a data base. \n",
@@ -14,6 +15,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "e14aa834-59c2-4f13-af01-dcd653505350",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -23,6 +25,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "d8f29718-cf71-4f84-b4be-3e1e3c4b8786",
    "metadata": {},
    "source": [
     "We load a dataset and get a handle on its unique *air* variable."
@@ -31,6 +34,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d60b6b3a-2a1e-4094-94b2-9cc8e5ea5242",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -41,6 +45,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "63da0ac9-3b01-4c55-8855-6436e4575aca",
    "metadata": {},
    "source": [
     "We want to better understand the temporal evolution of the air temperature over different latitudes compared to a baseline. The data pipeline we build includes:\n",
@@ -57,6 +62,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "5f7905ce-da82-43f2-8b27-84c5b868a588",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -78,6 +84,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "61d07327-08ee-45c4-b5cc-c08adf50f046",
    "metadata": {},
    "source": [
     "Without `.interactive()` we would manually change the values of `LATITUDE` and `ROLLING_WINDOW` to see how they affect the pipeline output. Instead we create two widgets with the values we expect them to take, we are basically declaring beforehand our parameter space. To create widgets we import [Panel](https://panel.holoviz.org) and pick two appropriate widgets from its [Reference Gallery](https://panel.holoviz.org/reference/index.html#widgets)."
@@ -86,6 +93,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "81684639-5d17-43aa-90b3-2590ed951272",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -97,6 +105,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "a49cb2c6-2e69-4a17-9ca3-ceb918460765",
    "metadata": {},
    "source": [
     "Now we instantiate an *Interactive* object by calling `.interactive()` on our data. This object mirrors the underlying object API, it accepts all of its natural operations. We replace the data by the interactive object in the pipeline, and replace the constant parameters by the widgets we have just created."
@@ -105,6 +114,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "55524639-5d5d-40c1-b76f-11da152fc6bd",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -114,6 +124,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "6f63c03e-79c2-4a6c-9203-2b4727894228",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -132,6 +143,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "4bbe8553-f79c-4e46-9a58-93b7cdb3e92f",
    "metadata": {},
    "source": [
     "You can see that now the pipeline when rendered doesn't only consist of its output, it also includes the widgets that control it. Change the widgets' values and observe how the output dynamically updates.\n",
@@ -144,6 +156,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "83e20794-0261-46f8-a094-1903937de550",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -154,6 +167,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "c458f2a3-eeca-477f-b7c1-6b53e4d0f18c",
    "metadata": {},
    "source": [
     "For information on using `.interactive()` take a look at the [User Guide](../user_guide/Interactive.ipynb)."

{hvplot-0.9.1rc1/hvplot/examples/reference/pandas → hvplot-0.9.2/examples/reference/tabular}/andrewscurves.ipynb

@@ -3,6 +3,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d8d7bf92-ae63-4122-9457-10c9ada6c6f1",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -11,6 +12,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "915da73a-0a5f-4a40-aa4b-a65a6002c3e9",
    "metadata": {},
    "source": [
     "Andrews curves provides a mechanism for visualising clusters of multivariate data.\n",
@@ -27,6 +29,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d85a9c83-bd5d-4ac2-b1a0-0bb451a484e9",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -38,6 +41,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "780fc986-819b-4882-9c44-113b9a211d97",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -47,6 +51,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "4c721441-ecf3-4178-a55f-d43eed7d00a5",
    "metadata": {},
    "outputs": [],
    "source": [

{hvplot-0.9.1rc1/examples/reference/pandas → hvplot-0.9.2/examples/reference/tabular}/lagplot.ipynb

@@ -3,6 +3,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "cb5dd3db-78c4-4a01-ba07-37f718f7425a",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -13,6 +14,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "c7af165e-4231-49ea-81d7-d07ad81a05da",
    "metadata": {},
    "source": [
     "Lag plots are most commonly used to look for patterns in time series data."
@@ -20,6 +22,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "815a51ab-5f61-4bea-bb56-e11a0f117718",
    "metadata": {},
    "source": [
     "Given the following time series:"
@@ -28,6 +31,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "283adbd9-3c42-4cb7-8c57-1d0e9fe1d25f",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -40,6 +44,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "8a877a7d-11cb-4bcb-81e4-3936f061ba65",
    "metadata": {},
    "source": [
     "A lag plot with `lag=1` returns:"
@@ -48,6 +53,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "52be318e-fccd-461d-9813-c231b6f2997c",
    "metadata": {},
    "outputs": [],
    "source": [

{hvplot-0.9.1rc1/examples/reference/pandas → hvplot-0.9.2/examples/reference/tabular}/parallelcoordinates.ipynb

@@ -3,6 +3,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "98539b4c-af81-4ad7-9fe5-8e1b828ee3d8",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -11,6 +12,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "0b7674d1-b972-4b43-9e96-18c0d0fcc125",
    "metadata": {},
    "source": [
     "Parallel coordinates are a common way of visualizing and analyzing high-dimensional datasets.\n",
@@ -21,6 +23,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "b524875d-aaa6-40da-8b1a-9f42f636da6a",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -32,6 +35,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "02fa9997-0c52-4ee8-890f-9ce2a6352e3f",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -41,6 +45,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "c737ec55-2c45-40dd-92d0-69464607bf7f",
    "metadata": {},
    "outputs": [],
    "source": [

{hvplot-0.9.1rc1/hvplot/examples/reference/pandas → hvplot-0.9.2/examples/reference/tabular}/scattermatrix.ipynb

@@ -3,6 +3,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "c092a604-c386-4dda-bc90-0ff11a8f880f",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -13,6 +14,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "1793d412-0d1e-4c8e-b470-ca978d5a53e2",
    "metadata": {},
    "source": [
     "`scatter_matrix` shows all the pairwise relationships between the columns of your data. Each non-diagonal entry plots the corresponding columns against another, while the diagonal plot shows the distribution of the data within each individual column.\n",
@@ -23,6 +25,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "9d6cb81d-7f65-41de-8386-26479e41ddd4",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -34,6 +37,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "91efa178-7cb4-4dbe-8730-59a2864cdf9a",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -42,6 +46,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "38913fbf-4982-4b82-bf81-01bb33faf8a0",
    "metadata": {},
    "source": [
     "The `chart` parameter allows to change the type of the *off-diagonal* plots."
@@ -50,6 +55,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "a4f72f5f-b9a1-41ce-b00d-59fad1b01b54",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -58,6 +64,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "11943cd6-7d10-4990-9de6-18402c4c42a8",
    "metadata": {},
    "source": [
     "The `diagonal` parameter allows to change the type of the *diagonal* plots."
@@ -66,6 +73,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d46fd8d8-bf72-45fe-9faf-a85c1239d21e",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -74,6 +82,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "3d13318b-b96c-4e62-b237-5202e5108a44",
    "metadata": {},
    "source": [
     "Setting `tools` to include a selection tool like `box_select` and an inspection tool like `hover` permits further analysis."
@@ -82,6 +91,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "135bdf59-c2c5-4253-b9a0-a786623db591",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -91,6 +101,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d4315596-0a9e-4c00-a0d3-c8f3a01b9518",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -99,6 +110,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "a8b4cef5-25ea-4129-ab0e-7cc6c36d3451",
    "metadata": {},
    "source": [
     "The `c` parameter allows to colorize the data by a given column, here by `'CAT'`. Note also that the `diagonal_kwds` parameter (equivalent to `hist_kwds` in this case or `density_kwds` for *kde* plots) allow to customize the diagonal plots."
@@ -107,6 +119,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "ba178ac7-936e-4585-964b-34a99b711108",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -116,6 +129,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "8a97b3bc-0053-41b6-a71a-70ceec9e3341",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -124,6 +138,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "eaa67050-09ad-4c79-9b01-03dd96a6bada",
    "metadata": {},
    "source": [
     "Scatter matrix plots may end up with a large number of points having to be rendered which can be challenging for the browser or even just crash it. In that case you should consider setting to `True` the `rasterize` (or `datashade`) parameter that uses [Datashader](https://datashader.org/) to render the off-diagonal plots on the backend and then send more efficient image-based representations to the browser.\n",
@@ -134,6 +149,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "ed43bbf1-4c62-4a80-b044-970c235727a0",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -142,6 +158,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "c50ec422-baf4-43d4-9f84-a8d74315b7e6",
    "metadata": {},
    "source": [
     "When `rasterize` (or `datashade`) is toggled it's possible to make individual points more visible by setting `dynspread=True` or `spread=True`. Head over to the [Working with large data using datashader](https://holoviews.org/user_guide/Large_Data.html) guide of [HoloViews](https://holoviews.org/index.html) to learn more about these operations and what parameters they accept (which can be passed as `kwds` to `scatter_matrix`)."
@@ -150,6 +167,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "e4974565-3c21-462c-b762-c5719d29c221",
    "metadata": {},
    "outputs": [],
    "source": [

{hvplot-0.9.1rc1 → hvplot-0.9.2}/examples/reference/xarray/hist.ipynb

@@ -14,7 +14,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "`hist` is often a good way to start looking at data to get a sense of the distribution. Similar methods include [`kde`](kde.ipny) (also available as `density`)."
+    "`hist` is often a good way to start looking at data to get a sense of the distribution. Similar methods include [`kde`](kde.ipynb) (also available as `density`)."
    ]
   },
   {

{hvplot-0.9.1rc1 → hvplot-0.9.2}/examples/user_guide/Geographic_Data.ipynb

@@ -48,7 +48,7 @@
    "source": [
     "### Plotting points\n",
     "\n",
-    "If we want to overlay our data on geographic maps or reproject it into a geographic plot, we can set ``geo=True``, which declares that the data will be plotted in a geographic coordinate system.  The default coordinate system is the ``PlateCarree`` projection, i.e., raw longitudes and latitudes. If the data is in another coordinate system, you will need to [declare an explicit ``crs``](#Declaring-a-CRS) as an argument, in which case `geo=True` is assumed.  Once hvPlot knows that your data is in geo coordinates, you can use the ``tiles`` option to overlay a the plot on top of map tiles."
+    "If we want to overlay our data on geographic maps or reproject it into a geographic plot, we can set ``geo=True``, which declares that the data will be plotted in a geographic coordinate system.  The default coordinate system is the ``PlateCarree`` projection, i.e., raw longitudes and latitudes. If the data is in another coordinate system, you will need to [declare an explicit ``crs``](#declaring-a-crs) as an argument, in which case `geo=True` is assumed.  Once hvPlot knows that your data is in geo coordinates, you can use the ``tiles`` option to overlay a the plot on top of map tiles."
    ]
   },
   {

{hvplot-0.9.1rc1 → hvplot-0.9.2}/examples/user_guide/NetworkX.ipynb

@@ -77,7 +77,7 @@
    "cell_type": "markdown",
    "metadata": {},
    "source": [
-    "The ``hvnx`` namespace also makes ``save`` and ``show utilities available to save the plot to HTML or PNG files or display it in a separate browser window when working in a standard Python interpreter."
+    "The `hvnx` namespace also makes `save` and `show` utilities available to save the plot to HTML or PNG files or display it in a separate browser window when working in a standard Python interpreter."
    ]
   },
   {

{hvplot-0.9.1rc1/hvplot → hvplot-0.9.2}/examples/user_guide/Pandas_API.ipynb

@@ -82,13 +82,6 @@
     "df3.plot(x='A', y='B')"
    ]
   },
-  {
-   "cell_type": "markdown",
-   "metadata": {},
-   "source": [
-    "**Note** For more formatting and styling options, see [formatting](#plot-formatting) below."
-   ]
-  },
   {
    "cell_type": "markdown",
    "metadata": {},

{hvplot-0.9.1rc1/hvplot → hvplot-0.9.2}/examples/user_guide/Viewing.ipynb

@@ -172,6 +172,18 @@
    "source": [
     "hvplot.save(plot, 'test.png')"
    ]
+  },
+  {
+   "cell_type": "code",
+   "execution_count": null,
+   "metadata": {},
+   "outputs": [],
+   "source": [
+    "from pathlib import Path\n",
+    "\n",
+    "Path('test.html').unlink(missing_ok=True)\n",
+    "Path('test.png').unlink(missing_ok=True)"
+   ]
   }
  ],
  "metadata": {

hvplot-0.9.2/hvplot/.version

@@ -0,0 +1 @@
+{"git_describe": "v0.9.2-0-g4e9f860", "version_string": "0.9.2"}

{hvplot-0.9.1rc1 → hvplot-0.9.2/hvplot}/examples/getting_started/interactive.ipynb

@@ -2,6 +2,7 @@
  "cells": [
   {
    "cell_type": "markdown",
+   "id": "66dddf49-c70a-4ed1-98e7-76703b82fa34",
    "metadata": {},
    "source": [
     "hvPlot isn't only a plotting library, it is dedicated to make data exploration easier. In this guide you will see how it can help you to get better control over your data pipelines. We define a *data pipeline* as a series of commands that *transform* some data, such as aggregating, filtering, reshaping, renaming, etc. A data pipeline may include a *load* step that will provide the input data to the pipeline, e.g. reading the data from a data base. \n",
@@ -14,6 +15,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "e14aa834-59c2-4f13-af01-dcd653505350",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -23,6 +25,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "d8f29718-cf71-4f84-b4be-3e1e3c4b8786",
    "metadata": {},
    "source": [
     "We load a dataset and get a handle on its unique *air* variable."
@@ -31,6 +34,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d60b6b3a-2a1e-4094-94b2-9cc8e5ea5242",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -41,6 +45,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "63da0ac9-3b01-4c55-8855-6436e4575aca",
    "metadata": {},
    "source": [
     "We want to better understand the temporal evolution of the air temperature over different latitudes compared to a baseline. The data pipeline we build includes:\n",
@@ -57,6 +62,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "5f7905ce-da82-43f2-8b27-84c5b868a588",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -78,6 +84,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "61d07327-08ee-45c4-b5cc-c08adf50f046",
    "metadata": {},
    "source": [
     "Without `.interactive()` we would manually change the values of `LATITUDE` and `ROLLING_WINDOW` to see how they affect the pipeline output. Instead we create two widgets with the values we expect them to take, we are basically declaring beforehand our parameter space. To create widgets we import [Panel](https://panel.holoviz.org) and pick two appropriate widgets from its [Reference Gallery](https://panel.holoviz.org/reference/index.html#widgets)."
@@ -86,6 +93,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "81684639-5d17-43aa-90b3-2590ed951272",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -97,6 +105,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "a49cb2c6-2e69-4a17-9ca3-ceb918460765",
    "metadata": {},
    "source": [
     "Now we instantiate an *Interactive* object by calling `.interactive()` on our data. This object mirrors the underlying object API, it accepts all of its natural operations. We replace the data by the interactive object in the pipeline, and replace the constant parameters by the widgets we have just created."
@@ -105,6 +114,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "55524639-5d5d-40c1-b76f-11da152fc6bd",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -114,6 +124,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "6f63c03e-79c2-4a6c-9203-2b4727894228",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -132,6 +143,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "4bbe8553-f79c-4e46-9a58-93b7cdb3e92f",
    "metadata": {},
    "source": [
     "You can see that now the pipeline when rendered doesn't only consist of its output, it also includes the widgets that control it. Change the widgets' values and observe how the output dynamically updates.\n",
@@ -144,6 +156,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "83e20794-0261-46f8-a094-1903937de550",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -154,6 +167,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "c458f2a3-eeca-477f-b7c1-6b53e4d0f18c",
    "metadata": {},
    "source": [
     "For information on using `.interactive()` take a look at the [User Guide](../user_guide/Interactive.ipynb)."

{hvplot-0.9.1rc1/examples/reference/pandas → hvplot-0.9.2/hvplot/examples/reference/tabular}/andrewscurves.ipynb

@@ -3,6 +3,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d8d7bf92-ae63-4122-9457-10c9ada6c6f1",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -11,6 +12,7 @@
   },
   {
    "cell_type": "markdown",
+   "id": "915da73a-0a5f-4a40-aa4b-a65a6002c3e9",
    "metadata": {},
    "source": [
     "Andrews curves provides a mechanism for visualising clusters of multivariate data.\n",
@@ -27,6 +29,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "d85a9c83-bd5d-4ac2-b1a0-0bb451a484e9",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -38,6 +41,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "780fc986-819b-4882-9c44-113b9a211d97",
    "metadata": {},
    "outputs": [],
    "source": [
@@ -47,6 +51,7 @@
   {
    "cell_type": "code",
    "execution_count": null,
+   "id": "4c721441-ecf3-4178-a55f-d43eed7d00a5",
    "metadata": {},
    "outputs": [],
    "source": [