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, -- Arian Ott [email protected]
signature.asc
Description: This is a digitally signed message part.
