Hmm...
So dask doesn't think jinja is required for base functionality. It's a
dependency for an extended extras.
>From dask's setup.py
extras_require = {
"array": ["numpy >= 1.18"],
"bag": [], # keeping for backwards compatibility
"dataframe": ["numpy >= 1.18", "pandas >= 1.0"],
"distributed": ["distributed == 2021.08.1"],
"diagnostics": [
"bokeh >= 1.0.0, != 2.0.0",
"jinja2",
],
"delayed": [], # keeping for backwards compatibility
}
At dask's end jinja should probably be a suggests or recommends, but
since you can use dask without needing widgets I'm not 100% sure jinja
needs to build-dependency.
(Do widgets even work on Debian? Last time I tried jupyter widgets I
couldn't get them to work.)
Diane
On Sat, 2021-09-04 at 22:36 +0200, Drew Parsons wrote:
> Package: python3-dask
> Version: 2021.08.1+dfsg-1
> Severity: serious
> Justification: debci
> Control: affects -1 src:python-xarray
>
> dask imports from jinja2 in
> /usr/lib/python3/dist-packages/dask/widgets/widgets.py, but
> Depends: python3-jinja2 has not been declared.
>
> dask's own tests are apparently not testing widget since they're
> passing, but
> the error is triggered by python-xarray, see
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-xarray/15028004/log.gz
>
>
> I guess debian/control needs Build-Depends: python3-jinja2
> and then dh_python will take care of the Depends field in the binary
> package.
>
> Drew
>
