Scopes & cleanup¶

Scopes give you a way to say: “for this unit of work (request/job), reuse scoped services and clean them up at the end.”

Creating a scope¶

Use diwire.Container.enter_scope() as a context manager:

See the runnable scripts in Scopes (Scope basics section).

Scoped lifetime¶

To share an instance within a scope, register it as Lifetime.SCOPED and provide a scope name:

See the runnable scripts in Scopes (SCOPED lifetime section).

Generator factories (deterministic cleanup)¶

When you need cleanup (close a session, release a lock, return a connection to a pool), use a generator factory. diwire will close the generator when the scope exits, running your finally block.

See the runnable scripts in Scopes (Generator factories section).

Nested scopes¶

Scopes can be nested. A nested scope can still access services registered for its parent scopes.

See the runnable scripts in Scopes (Nested scopes section).

Imperative close¶

You can also manage scopes imperatively:

scope = container.enter_scope("request")
try:
    ...
finally:
    scope.close()

There are also convenience methods for closing active scopes by name: