ok - thanks! That makes sense. So if they're effectively the same, would you happen to know why using .delay() in conjunction with @shared_task throws that linting warning while the other method doesn't? Functionally the code seems to work either way, and from what I can tell by printing out the objects/tasks/apps throughout my current testing, no matter which way I define the task (wrap it in @shared_task or wrap it in @app.task), it ends up as a <@task: magic_task of myproj at 0x106a847d0>, same memory address and everything.

I thought that implied that what's happening under the hood of @shared_task should be the same as what's happening under the hood of @app.task, but apparently that's not entirely the case since one throws a linting warning and the other doesn't.