Skip to content
This repository was archived by the owner on Jun 5, 2023. It is now read-only.

handle jobs queued by Ruby Resque with no module#142

Merged
binarymatt merged 1 commit intobinarymatt:masterfrom
Affectiva:resque_compatibility
May 13, 2015
Merged

handle jobs queued by Ruby Resque with no module#142
binarymatt merged 1 commit intobinarymatt:masterfrom
Affectiva:resque_compatibility

Conversation

@caboteria
Copy link
Contributor

Ruby compatibility: Resque sends just a class name and not a module name
so if I use Resque to queue a ruby class called "Worker" then Pyres will
throw a "ValueError: Empty module name" exception. To avoid that, if
there's no module name in the json then we'll use the class name as a
module name.

Ruby compatibility: Resque sends just a class name and not a module name
so if I use Resque to queue a ruby class called "Worker" then Pyres will
throw a "ValueError: Empty module name" exception.  To avoid that, if
there's no module name in the json then we'll use the class name as a
module name.
binarymatt added a commit that referenced this pull request May 13, 2015
handle jobs queued by Ruby Resque with no module
@binarymatt binarymatt merged commit d9c0bd4 into binarymatt:master May 13, 2015
@caboteria caboteria deleted the resque_compatibility branch May 13, 2015 21:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants