On Mon, Dec 29, 2008 at 5:46 PM, Erich <[email protected]> wrote: > Also, I did notice one error that should be fixed soon on github: job > should be an attribute of the ServerConn class, not the instance, so > you should only need to set it once per runtime, not once per > connection object. (Once again, this is flexible, due to the nature of > objects in python...).
I can imagine wanting to have different job implementations for different connections. I agree that setting the job attribute on the ServerConn class makes sense for most uses, but perhaps it could be overridable with an optional keyword arg to the ServerConn constructor. kr --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
