Iif you do mrq-run mrq-test.Fetch '{"url":"xx"}' it will be run in the same python process, but if you do mrq-run --async mrq-test.Fetch it will be queued and return the job ID.
From the code the default is different, send_task() is async by default but can be used with send_task(sync=True).
We need to rename a couple things there to be consistent :)
Also, from mrq.queue import send_task is not the best we can do.
Iif you do mrq-run mrq-test.Fetch '{"url":"xx"}' it will be run in the same python process, but if you do mrq-run --async mrq-test.Fetch it will be queued and return the job ID.
From the code the default is different, send_task() is async by default but can be used with send_task(sync=True).
We need to rename a couple things there to be consistent :)
Also,
from mrq.queue import send_taskis not the best we can do.