Skip to content

docs: say Celery tasks resolve from their own app's container #712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lesnik512 merged 1 commit into from
Oct 17, 2026
Merged

docs: say Celery tasks resolve from their own app's container #712

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/integrations/celery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,8 +66,9 @@ def run_report(report: typing.Annotated[Report, FromDI(Report)]) -> str:
`setup_di(app, container)` registers the container for the app and connects Celery's
worker signals that open and close it. `@inject` builds a `Scope.REQUEST` child container
for each task call and resolves `FromDI`-annotated parameters from it. It looks the
container up through Celery's `current_app` at call time, so it resolves against
whichever app is active.
container up through the running task's app, so a task resolves from its own app's
container even when another app is current. Outside a task it falls back to Celery's
`current_app`. Before modern-di-celery 4.2.2, the lookup always went through `current_app`.

Celery closes containers with `close_sync()`, both the per-task child and the root at
worker shutdown. Finalizers must therefore be sync: an async finalizer makes the close
Expand Down
Loading