* Package name    : pymatting
    Version         : 1.1.13
    Upstream Author : Thomas Germer, Tobias Uelwer, Richard Belger,
Stefan Harmeling
* URL             : https://github.com/pymatting/pymatting
* License         : MIT
    Programming Lang: Python
    Description     : A Python library for alpha matting

PyMatting is a Python library for alpha matting. Alpha matting is the
process
of estimating the foreground color and alpha matte from an image and a
trimap. This library implements several state-of-the-art algorithms for
this task.

I am packaging this as a dependency for python-rembg.

Hello Gioele,

I'm making good progress with 'rembg' and its dependency 'pymatting'.

'rembg' depends on 'pymatting', which in turn depends on 'numba'. The current
version of 'numba' in sid is restricted to Python 3.13 [1].

Consequently, I have configured 'pymatting' to skip Python 3.14 for now using
X-Python3-Version.

This means 'rembg' will also be restricted to Python 3.13 as long as 'numba'
is not available in 3.14.

Furthermore, I discovered that there is a huge version mismatch between PyPi,
Github master branch and the release tags.

As of now, following construct exists:
* Github Tags: 1.1.13 [2]
* PyPi: 1.1.14 [3]
* Master branch: 1.1.15 [4]

On GitHub, version 1.1.13 still uses setup.py, whereas the master branch uses
pyproject.toml.

I opened an issue upstream to address the version discrepancies in pypi and
GitHub releases  so that upstream is aware of the current situation.

My current workflow is to clone the repo in salsa and import it to my machine
using gbp clone --pristine-tar.

Depending on the upstream response, I propose the following plan:

a) Upstream releases v1.1.14 on Github: Proceed packaging and filing an RFS
b) Upstream does not release v1.1.14 on GitHub: : I will change the watchfile
from GitHub to PyPI, as this represents the official release channel.

Note: If the PyPI tarball lacks the test data present in Git, I will likely
have to create a repackaged (+dfsg) version to enable the test suite.

What do you think?

References:
[1] https://packages.debian.org/sid/python3-numba
[2]  https://github.com/pymatting/pymatting/releases
[3] https://pypi.org/project/PyMatting/
[4] https://github.com/pymatting/pymatting/blob/master/pyproject.toml#L7

Best,

Hello,

This email serves as documentation of the upstream interaction.

After addressing the version mismatch between pypi, GitHub Tags and the actual
master branch, upstream has created a v1.1.15 tag, so that everything is in
sync now.

Furthermore, upstream pointed out that pymatting has CyPy as optional
dependencies. Due to the complexity of CyPy, we came to the conclusion that
packaging pymatting without optional dependencies is a good way forward.

Link to GitHub issue: https://github.com/pymatting/pymatting/issues/97

Best,

This email serves as documentation of the upstream interaction. I have already
sent this email once but havent received any response from the BTS. I will
resend this email in order to ensure it arrived the BTS:

---- BEGIN EMAIL ----

Hello,

After addressing the version mismatch between pypi, GitHub Tags and the actual
master branch, upstream has created a v1.1.15 tag, so that everything is in
sync now.

Furthermore, upstream pointed out that pymatting has CyPy as optional
dependencies. Due to the complexity of CyPy, we came to the conclusion that
packaging pymatting without optional dependencies is a good way forward.

Link to GitHub issue: https://github.com/pymatting/pymatting/issues/97

Best,
-- 
Arian Ott
arian.ott@ieee.org

---- END EMAIL ----

Hello,

because of autopkgtests which are caused by numba's version constraints, I put
the packaging of pymatting on hold.

Thanks for your understanding.

Regards,