Selwin Ong

It won't work because under runserver, that function would just be a regular function and not a job (get_current_job would always return None). What you can do is to get...

It's not currently possible to ask workers about the job they're working on. You're right in that nvie/rq#269 is what you'll need. I think it's a reasonable feature request :)

Ideally, there's also an option to delete all and not just the 50 selected jobs from the queue, similar to how Django's admin behaves. I'd be happy to accept a...

We should check that if `interval` is passed into RQ, the job's `result_ttl` must be set to infinite until the very last iteration of the job. Could you please open...

@meteozond the main purpose of `django-rq` is to provide convenience. For me, being able to centrally define the queues and refer to them by name, is a big win because...

Yeah, I think we should do that. Mind opening a PR for this?

Sorry, I don't think this is the right approach as this would break down if you have a large (millions of jobs) queue. One way we can solve this is...

RQ actually already has an "rq suspend" command which is not documented. This command pauses job execution so you can pause workers before shutting it down in Heroku. We should...

Did you mean that `scheduled.cancel(job)` fails? Can you provide a failing test case or traceback of the crash?

The main reason is that I tried to keep this consistent with `Queue`'s API. You could certainly argue the same thing about `Queue` being a central component that routes jobs...