Bug#570210: Module should be named 'debian', not 'debian_bundle'

[Stefano Zacchiroli]

On Wed, Feb 17, 2010 at 11:37:25AM +0100, Julian Andres Klode wrote:
> The module should be called 'debian' and not 'debian_bundle', in order
> to get 'import debian' working. This is Python Policy, section 2.2. Otherwise,
> the package may also be renamed to 'python-debian-bundle' to somehow match
> the Policy in a better way.

Eh eh, it was about time that issue got raised :-)

So, we basically have two possibilities: rename the module (to
"debian"), rename the package (to "python-debian-bundle"). I've
personally *never* liked "debian_bundle": it might be correct, but it is
not intuitive at all.

I'm hence for renaming the module and then providing, just for a
release, a transition path with an empty "debian_bundle" module which
imports "debian" and outputs a deprecation warning.

What do others think?

Cheers.

-- 
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-python-debian-maint/attachments/20100217/70df4947/attachment.pgp>