Re: RFC: python-imgviz: Repository out of sync with Archive

Arian Ott <[email protected]> Tue, 20 Jan 2026 10:44:28 +0100
Newsgroups gmane.linux.debian.devel.python
Message-ID <[email protected]>
> Yes, that is quite common.  You can create debian/unstable and debian/
> experimental branches in your Salsa repository and release from both.
> 

I began the implementation in that regard and modernised the package 
according to current standards. Everything seems very promising.

However, I came across a different issue with python-imgviz. In newer 
versions, imgviz depends on the package cmap.

Cmap was released in 2023 to provide a minimal library which gives 
access to the colour maps of large ecosystems such as matplotlib.

At the moment cmap only depends on numpy but has heavy dependency groups 
[1].

Cmap itself is released under the BSD-3 license but includes 10 
different licenses. [2]

The documentation clearly states that cmap can provide "[...] all of the 
colormaps in matplotlib, [...] (and more), with no dependencies beyond 
numpy".[3]

My next step is to validate the licenses of cmap and the code to verify 
if potential licensing issues arise.

If no issues arise I will file an ITP, package cmap first, where 
possible exclude all of the dependency groups, and then continue my work 
with python-imgviz.

If there are issues, I will approach the maintainers of imgviz to 
resolve those concerns.


Best,

--
Arian Ott
[email protected]


References:

[1] https://github.com/pyapp-kit/cmap/blob/main/pyproject.toml#L29-L76
[2] https://github.com/pyapp-kit/cmap/tree/main/LICENSE
[3] https://cmap-docs.readthedocs.io/en/stable/#overview
OpenPGP_signature.asc (application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQS3O5yelQb/Rpa5Q6xDraCJlFsAhQUCaW9OfAAKCRBDraCJlFsA
hTEOAP410vj+wLMbbylgfSc4/GDdKWcgWPwK2s0CKYvjKx9h8QD+MxNcuMcQ3Tft
1drdQyIy2FMTUsjAxuryI3Sv0lQv/gI=
=l6El
-----END PGP SIGNATURE-----