Inconsistency in source package naming for python modules

[Thomas Goirand <zigo@debian.org>]

Hi,

Over the last months, I've seen lots of inconsistency in the source
package naming scheme in the python module maintained in the team.
Sometimes, module X will have its source package called python-X or just X.

If we have a python module named X, then IMO, we should stick to call
the source package python-X, and not just X. Why? Because AFAICT it
seems that there's a consensus in Debian that, if a package is producing
a single binary, then its source package should have the same name.

It isn't my intention to fix mistakes already made (IMO, too much work
for not enough rewards), but I wanted to raise this topic to check if
others have the same opinion, and to make sure we have this in the
python policy (in one way or the other). Thoughts anyone?

Cheers,

Thomas Goirand (zigo)