[Python-modules-team] Bug#620469: Bug#620496

[Clint Byrum]

Excerpts from Oxan van Leeuwen's message of Mon Apr 18 11:49:18 -0700 2011:
> Hi Clint,
> 
> On 03-04-11 18:53, Clint Byrum wrote:
> > I think the way to go is to drop __init__.py from
> > python-gearman.libgearman, and make it depend on python-gearman, since
> > it is a sub-module of the gearman namespace.
> > 
> > I haven't been able to make gearman.libgearman work properly without
> > the __path__ changes, though I'm not entirely sure why as I'm sort of a
> > python extension novice. If anyone *can* make that work, then we don't
> > even need the change suggested above.
> 
> I did some more testing and gearman.libgearman actually works without the
> __path__ changes, when it's installed in one of the standard Debian locations.
> During compilation it's not, so it needs the __path__ changes then.
> 
> The problem with implementating that is python-gearman uses dh_python2 while
> gearman.libgearman uses python-support, which results in the bytecode files
> (.pyc) being installed into different directories. When I converted
> gearman.libgearman to dh_python2 both packages work fine. Do you agree with this
> solution?

Thats great news, and yes I agree with the solution completely. I
had actually already begun porting the package to dh_python2 in the
bzr branch:

https://code.launchpad.net/~clint-fewbar/gearman-interface/debian-packaging

> 
> I've attached the patch that I used for testing gearman.libgearman using
> dh_python. You'll probably need to make some more changes, but maybe you can use
> this.

I've added some of your tweaks to the branch. However, its not clear to
me the reason for these two additions to debian/rules:

    rm -rf python3/build/
    +   rm -rf python3/gearman/_libgearman*so
    +   rm -rf python3/gearman/__pycache__
        [ ! -f python/libgearman.c.orig ] || mv -f python/libgearman.c.orig python/libgearman.c

I was hoping you could explain those. Once I can explain what that is
in debian/changelog, I'll get it uploaded.