What steps will reproduce the problem?
1. Try running this client with beanstalkd 0.6
A new release of beanstalkd is out, and with it, protocol changes. Update
the protohandler.py to play nicely.
Original issue reported on code.google.com by sophac...@gmail.com on 3 Jan 2008 at 3:25
Original issue reported on code.google.com by
sophac...@gmail.com
on 3 Jan 2008 at 3:25