Bug#736523: Indeed, python-concurrent.futures is the same
Hi,
Indeed, that's the same source package.
Indeed as well, there's lots of problems in the current package in
Debian. The current maintainer, Sandro Tosi <morph@debian.org>,
completely removes the "futures" API.
As a consequence, there's no way for a normal package to use
concurrent.futures correctly. I have been stuck on the python-taskflow
for a long long time, not understanding what happened: it failed on most
of it's unit tests (a bit less than 200 failed unit tests) because of
this problem.
Here's the problems I saw in the version 2.1.6-1 of the package in Sid:
* python-concurrent.futures currently doesn't install itself at all
inside /usr/lib/python2.7, which I don't think makes it possible to use
it at all.
* Surprisingly, there's a patch to *not* install the "futures" python
module where upstream code is expecting it. I removed that.
* the sphinx doc isn't handled correctly. There's was
${sphinxdoc:Depends}, so not correct dependencies. Sandro: lintian must
have warned you about it, next time, please read the lintian report
before uploading.
* IMO, there's a missing Provides: python-futures, since that's what the
dh_python2 is adding as depends: when I build python-taskflow.
* the package is build-depending on python-support, which has been
deprecated in the favor of dh_python2. Please see:
https://wiki.debian.org/Python/TransitionToDHPython2
Since the package is team maintained, I've fixed all these problems and
just uploaded version 2.1.6-2 to Sid. I will ask for rejection of
python-futures by the FTP masters.
Cheers,
Thomas Goirand (zigo)
Reply to: