[Python-modules-team] Bug#822157: python-future hides and breaks python-configparser

Raphaël Hertzog hertzog at debian.org
Thu Apr 21 15:46:45 UTC 2016

Source: python-future
Version: 0.15.2-1
Severity: serious
Tags: upstream
User: devel at kali.org
Usertags: origin-kali
Control: forwarded -1 https://github.com/PythonCharmers/python-future/issues/118
Control: affects -1 python-configparser

python-future provides the "configparser" module and so does
the python-configparser package... unfortunately, nobodby caught
this as there is no file conflict (configparser/__init__.py on one side
and configparser.py on other side).

But package depending on python-configparser (and there are 7 of them)
can't use the backported configparser when python-future is installed.

Upstream has not yet dropped the module but I believe we should do it
in Debian and replace it with a dependency on python-configparser. They
are not 100% API compatible but you can't get it both ways and using
the 3.X API is the way forward anyway for anyone who is looking to use

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

More information about the Python-modules-team mailing list