Bug#836677: pysparse: still worth maintaining?

[Ghislain Vaillant]

I have had a look at updating the package to the newest upstream
release and fixing this FTBFS. However, I have got strong concerns as
to whether it is worth keeping this package maintained in the archive:

- The latest release on PyPI [1] is busted (missing files). The issue
was reported [2] but never addressed since.

- Latest activity on the upstream repository is from 2013. By now, I
expected upstream would have fixed the PyPI tarball, at least.

- No Python 3 support. A manual call to 2to3 on the Python sources
allows the build process to run, but fails at the compilation stage.

[1] https://pypi.python.org/pypi/pysparse
[2] https://sourceforge.net/p/pysparse/mailman/message/33117282/

Best regards,
Ghis