conflicts with gearman.libgearman

[SpamapS]

Hi! It seems this module and the libgearman module:

http://pypi.python.org/pypi/python3-libgearman/0.13.3

Conflict, but they don't need to.

the gearman/init.py in that file is just:

from pkgutil import extend_path
path = extend_path(path, name)

This is just to make python find the C extension.

If you were willing to add that file to init.py from this module, we could share the file, allowing users to have both installed.

[SpamapS]

To add some details (sorry I wrote that about 30 seconds before passing out to sleep), those two lines could be added to init.py, and then gearman.libgearman can depend on gearman, which makes sense given it plays it the same namespace. Eventually we might even modify the SWIG bindings to make sure the same constants are mapped from libgearman.

[mtai]

Hmmm I'm not sure what the canonical way of resolving conflicts like this are. It sounds to me that similarly python3-libgearman could similarly change their init.py to play nicely with python-gearman?

If you can find any other cases where lib authors resolve issues like this, please send them my way. I do want to play nicely but it sounds like a battle for namespaces here :) Would like to see some precedent.

Would a py3k version of python-gearman actually solve your problems?