Thanks for the detailed information

On Fri, 30 Aug 2019 07:16:43 +0000 Matthias Klose <d...@debian.org> wrote:
[...]
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.
> 
> - Convert your Package to Python3. This is the preferred option.  In
>   case you are providing a Python module foo, please consider dropping
>   the python-foo package, and only build a python3-foo package.  Please
>   don't drop Python2 modules, which still have reverse dependencies,
>   just document them.
>   
>   This is the preferred option.

The Python bindings are not really maintained much by upstream. It is possible 
to build the module for Python3 and I have placed the required changes for 
this in the Vcs debian/experimental branch.

But there are still some problems in the way how the binary strings must be 
handled for two function (decodeImage, encodeImage). I hope to be able to 
discuss this with upstream.

If upstream decides not to support python3 (or pyton at all), I might have to 
remove this package from Debian. But at the moment, there are now reverse 
dependencies to this package in Debian and the python-exactimage popcount is 
declining.

Kind regards,
        Sven

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to