#1074333 RFP: kaleido -- Static image export for web-based visualization libraries with zero dependencies

#1074333#5
Date:
2024-06-26 18:37:54 UTC
From:
To:
* Package name    : kaleido
  Version         : 0.2.1
  Upstream Contact: Plotly team
* URL             : https://github.com/plotly/Kaleido
* License         : expat
  Programming Lang: Python
  Description     : Static image export for web-based visualization libraries with zero dependencies

Kaleido is a cross-platform library for generating static images (e.g.
png, svg, pdf, etc.) for web-based visualization libraries, with a
particular focus on eliminating external dependencies. The project's
initial focus is on the export of plotly.js images from Python for use
by plotly.py, but it is designed to be relatively straight-forward to
extend to other web-based visualization libraries, and other programming
languages. The primary focus of Kaleido (at least initially) is to serve as
a dependency of web-based visualization libraries like plotly.py. As such,
the focus is on providing a programmatic-friendly, rather than user-friendly,
API.

This package is used by plotly and is needed for build python-cogent-doc documentation
package.

#1074333#12
Date:
2026-03-05 07:32:16 UTC
From:
To:
Hi,
I made some progress in packaging kaleido at
https://salsa.debian.org/python-team/packages/python-kaleido
within the debian python team.

I have also packaged some of its dependencies which were missing (choreographer,
logistro). The two dependencies are already in unstable.
(well, then the "with zero dependencies" is not true anymore)

I am *not* uploading kaleido yet to unstable, because kaleido and plotly
versions are supposed to be updated in sync. The version of kaleido I packaged
(1.2.0, i.e. the most recent one excluding the release candidates of 1.3.0) is
*not* compatible with the plotly version currently in unstable (plotly 5.20.0,
released 2024).

I have a draft of plotly 6.5.2
https://salsa.debian.org/ballarin/plotly
but I cannot upload it to unstable because plotly is *not* team maintained. I
have emailed the maintainer (also in cc here) asking him if he can have a look
at what I did on my fork.

Cheers,
Francesco