Bug#736523: python-future name clobbers existing Python package
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
Reply to: