Regardless of the status of concurrent.futures, there is an issue of consistency with the 'python-future' package name. There is already a 'future' package for python [1, 2], and the naming convention established in the Debian Python policy [3] would make users expect this package be available as 'python-future'.
[1] http://python-future.org/ [2] https://pypi.python.org/pypi/future [3] http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-package_names JC -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKADsbf9FuhsOdeg2quRjPV=QyTu=vmxyazf7z813y-t14o...@mail.gmail.com
