# PyData 2021 - Build polished, data-driven applications directly from your Pandas or XArray pipelines

**URL:** <https://discourse.holoviz.org/t/pydata-2021-build-polished-data-driven-applications-directly-from-your-pandas-or-xarray-pipelines/3017>\
**Category:** Showcase\
**Created:** [October 31, 2021, 1:23pm UTC](https://discourse.holoviz.org/t/pydata-2021-build-polished-data-driven-applications-directly-from-your-pandas-or-xarray-pipelines/3017 "2021-10-31T13:23:31Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![philippjfr](https://discourse.holoviz.org/user_avatar/discourse.holoviz.org/philippjfr/32/7_2.png) [@philippjfr](https://discourse.holoviz.org/u/philippjfr)\
**Post date:** [November 1, 2021, 8:16am UTC](https://discourse.holoviz.org/t/pydata-2021-build-polished-data-driven-applications-directly-from-your-pandas-or-xarray-pipelines/3017/4 "2021-11-01T08:16:09Z")

</div>

> [@Marc](#):
>
> Can `.interactive` cleverly understand what parts of the pipeline to recalculate?

Yes, it caches each step of the pipeline and only recomputes the parts downstream from the parameter that changed. It’s different from existing HoloViews and Panel pipelines in that it evaluates eagerly. This means that it always caches the most up-to-date result based on the parameters/widgets that feed into the pipeline. This is required so that we can accurately mirror the API of the object that is being wrapped. For very expensive calculations it might therefore not be entirely suitable but in those scenarios you could switch to dask, which would ensure that the actual execution is still lazy.

---

_[View the full topic](https://discourse.holoviz.org/t/pydata-2021-build-polished-data-driven-applications-directly-from-your-pandas-or-xarray-pipelines/3017)._