Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Added BEANSTALK_JOB_NAME pattern functionality to BeanstalkClient.call() #3

Open
wants to merge 2 commits into
from

Conversation

Projects
None yet
2 participants

BeanstalkClient.call() will use settings.BEANSTALK_JOB_NAME pattern to derive the function name if appname and jobname parameters are passed

Makes it easier for folks like me to manage staging and production servers with the same code base. I don't have to write special code to switch the function name given the deployment environment.

Also added some documentation to make the feature a bit clearer.

Note: I tried to select just one commit for this pull request, and to ignore some other changes I've made on my fork. I'm curious if I'm using this github feature correctly. If you decide to pull my changes, please let me know if it works.

Cole Krumbholz added some commits Sep 15, 2011

Cole Krumbholz BeanstalkClient.call() will use settings.BEANSTALK_JOB_NAME pattern t…
…o derive the function name if appname and jobname parameters are passed
c853072
Cole Krumbholz debug logging no longer writes out the arg for an event. I've been se…
…nding pickled data through the arg, and logger doesn't like printing that. Not sure if its a good idea to send pickled objects as beanstalk job arguments, will investigate further
dec8156
Owner

jonasvp commented Sep 22, 2011

Sorry for not getting back to you sooner. Looks good to me but I'll have to test it on my development machine. I'll let you know as soon as I tried it out.

Yeah, looks like this pull request included two commits, I was trying to only submit the last one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment