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

[John Wright]

On Wed, Feb 17, 2010 at 11:49:18AM +0100, Stefano Zacchiroli wrote:
> 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?

Agreed the debian_bundle name is a wart, so let's get rid of it (with a
transition phase).  Fixing the source tree might be funky, though.
We'll need an empty parent directory (lib?) since the "root" debian
directory is for packaging stuff.

-- 
John Wright <jsw at debian.org>