samuel/python-gearman

(maintenance transfered to http://github.com/Yelp/python-gearman) Gearman library for Python.

Description

Pure Python Gearman library.

See http://www.danga.com/gearman/ for more about Gearman.

Status

Stable and production ready.

Links

• home page
• documentation
• source

python-gearman's Issues

GearmanWorker cannot grab_job_uniq

The GearmanWorker does not have a mode in which it can issue a 'grab_job_uniq' request. This limits the utility of the python-gearman library. I forked the project and created a version of GearmanWorker that always issues a 'grab_job_uniq' request for my own needs. I am willing to modify my code to make this a parameter and submit a patch if anyone is interested in this functionality.

Let me know.

Thanks,
Talentless

Sample code incorrect

The sample code on http://samuelks.com/python-gearman/docs/ does not work against v2.02 of the library. For example:

from gearman import *
worker = GearmanWorker(["127.0.0.1"])
worker.register_function("echo", lambda job:job.arg)
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'GearmanWorker' object has no attribute 'register_function'

client = GearmanClient(["127.0.0.1"])
res = client.do_task(Task("echo", "foo"))
Traceback (most recent call last):
File "", line 1, in
AttributeError: 'GearmanClient' object has no attribute 'do_task'

I'm guessing this is because various methods and objects have been renamed.

Possible Memory Leak in client

If you have a gearman client like the one below and you want to submit many jobs, then you run into a memory leak.

client = gearman.GearmanClient(server)
for job in many_many_jobs:
req = client.submit_job(task, data)
...

The problem is in the python module client_handler.py, where every job is stored in a dictionary but never deleted.