Different interpretations of 'queue' between rq and django-rq. about django-rq HOT 2 CLOSED

I think you missed the point of my comment.

Out of the box, rq allows you an infinite number of queues from a single connection. django_rq takes away that ability unless you manually code the same connection string for every single queue you might ever use. It also requires you change the settings.py per queue, which seems silly to me when it is unnecessary.

I guess I just don't see how having to repeat the same connection information a half dozen times is better than allowing the user to just specify which one they want independent of the queue.

As for "how would rqworker know", I'd assume you'd want to either default to all queues, or just use an extra argument like 'python mange.py rqworker --all' to indicate you want them all. (With 'all' equaling the output of 'rq.Queue.all()')

from django-rq.

Hi @dragonpaw,

Not true that a Queue doesn't know anything about the underlying connection. See http://python-rq.org/docs/connections/ . If you don't specify the redis server to use in settings.py, you'll need to do (which is a lot of work):

from rq import use_connection
use_connection() # This says use connection = Redis('localhost', 6379, 0)
import django_rq
queue = django_rq.get_queue('default')
queue.enqueue(func)

Besides if you define wildcard queues in settings.py, how would python manage.py rqworker know which queues to listen on?

from django-rq.