Selwin Ong

> If you look at 0d3f7d8, you see that I switched to MyST. This is a Markdown flavor which supports rst features: I'm aware, but what I'm saying is I'd...

@rpkak please see my [comment here](https://github.com/rq/rq/issues/1313#issuecomment-860000008). Do you think this PR is still relevant?

> I currently distribute the code via scp and have to restart the workers so they update the imports but this is inconvenient when there is another job in progress....

The real fix is that if a job is canceled, it should also be removed from `ScheduledJobRegistry` so it doesn't get executed. Mind opening a PR for this?

So there are multiple ways we can go about this: 1. Use the new `on_success_callback` which automatically passes you the job instance, from which you can access `job.result` 2. Another...

> This is a little bit ugly, since you have to reach into RQ internals in bar. You are also unable to determine the argument type in bar without knowing...

I have mixed feelings about the `fetch_results` decorator because: 1. You actually still need to update your code to use previous job results. 2. The decorator changes your function's signature...

> I'm afraid I don't understand your proposed solution. Can you write some pseudo code for what the user would call when enqueueing and for the job function please? If...

Can't you use logging to redirect your output to stdout?

Yes, I think capturing job outputs in “job.output” is a good idea. I’d welcome a PR for this.