injected
Simple, type-safe dependency injection in idiomatic Python, inspired by FastAPI.
Injecting dependencies
from injected import depends, resolver
def get_a() -> int:
return 13
def get_b() -> int:
return 17
@resolver
def get_sum(
a: int = depends(get_a),
b: int = depends(get_b),
) -> int:
return a + b
assert get_sum() == 30
Seeding the context of a resolver
It's sometimes useful to be able to provide an already resolved value, making it available throughout the dependency graph. The canonical example of this is how FastAPI makes things like requests and headers available to all dependencies.
To use this pattern, you specify a sentinel function, get_global_value in the example
below, and then map it to a resolved value in a context passed to seed_context().
from injected import depends, resolver, seed_context
def get_global_value() -> int: ...
@resolver
def calculate_value(a: int = depends(get_global_value)) -> int:
return a + 13
seeded = seed_context(calculate_value, {get_global_value: 31})
assert seeded() == 44
Async dependencies and context managers
Dependencies can be any combination of async and non-async functions and context managers. Async dependencies are resolved concurrently, and are scheduled at the optimal time, as soon as their own dependencies are resolved.
Context managers are torn down upon exiting the entry-point function.
import asyncio
from collections.abc import AsyncIterator
from contextlib import asynccontextmanager
from injected import depends, resolver
async def get_a() -> int:
return 13
def get_b() -> int:
return 17
@asynccontextmanager
async def get_c() -> AsyncIterator[int]:
yield 23
@resolver
async def get_sum_async(
a: int = depends(get_a),
b: int = depends(get_b),
c: int = depends(get_c),
) -> int:
return a + b + c
@resolver
def get_sum_sync(
a: int = depends(get_a),
b: int = depends(get_b),
c: int = depends(get_c),
) -> int:
return a + b + c
assert asyncio.run(get_sum_async()) == 53
assert get_sum_sync() == 53
Metadata
Release files for injected 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| injected-0.3.0.tar.gz | 8.1 kB | With provenance | Details for injected-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| injected-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for injected-0.3.0-py3-none-any.whl |
Total release size: 14.8 kB
Release files / injected-0.3.0.tar.gz
| Download URL | injected-0.3.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8f9bd1c56c20f71fcf8288a198845aecc93649fbe613c9a564a0000b3c606346
|
|
BLAKE2b-256 checksum How to use checksums |
12f609ddab4be919d7a50dbf3cb69e320bac86f9f918861189ad83dd824cb20d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logRelease files / injected-0.3.0-py3-none-any.whl
| Download URL | injected-0.3.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fb5b50ae37adf00211f2cfad31a15d3f70219b6cd4adba9a86bedf3c1aa8b2ac
|
|
BLAKE2b-256 checksum How to use checksums |
e3c10174fd435131d0368a90bed2d5886d9b9fdf0e07fe1f976c0ca424853159
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logSecurity for injected 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for injected-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 24, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.