This release is a pre-release and may not be stable for production use.
cdi
stands for "cute dependency injector" I guess(?)
install
pip install cdi-di
AI statement
AI was not used nor will be used for any part of the library code, PRs generated by AI, look like AI generated code (low quality) will be rejected, only documentation AI PRs will be accepted
Dependency injection made easy
while some python dependency injectors require some setup and make some things
harder to understand for a simple dependency injection, cdi aims to simplify
dependency injection and be fast (relativly to python)
batteries
- forward reference resolver
Lazytype for circular depsContextvarsupportTransientfor nonsingleton instancesGenerics/TypeVarsupport- limited instances
- scope inheritance
- no injectable default implementation support
Explicit is better then implicit
the library tries to make you explicit with your typing without compromising readability or ease of use
import cdi
# this container will contain its own registered types
ctr = cdi.Container()
# register this function as a factory
# for the `int` type
@cdi.Injectable(ctr)
def get_int() -> int:
return 100
# register `Foo` as injectable
# so we can create instances
@cdi.Injectable(ctr)
class Foo:
def __init__(self, number: int) -> None:
self.number = number
# create a scope that will have access to registered
# types in `ctr` then get an instance of `Foo`
scope = cdi.Scope(cdi)
instance = scope.get_instance(Foo)
assert instance.number == 100
import cdi
from typing import Generic, TypeVar
from collection.abc import Sequence
T = TypeVar('T')
ctr = cdi.Container()
class MyBase(Generic[T]):
def __init__(self, field: T) -> None:
self.field = field
@cdi.Injectable(ctr)
class MyType(MyBase[str]):
pass
@cdi.Injectable(ctr)
def name_generator() -> str:
return "foo"
scope = cdi.Scope(__name__, container=ctr)
instance = scope.get_instance(MyType)
assert instance.field == "foo"
ctr = cdi.Container()
class Foo(Generic[T]):
def __init__(self, v: T):
self.v = v
cdi.Injectable(ctr).register("hello world")
cdi.Injectable(ctr).register(100)
scope = Scope(__name__, container=ctr)
assert scope.get_instance(Foo[int]).v == 100
assert scope.get_instance(Foo[str]).v == "hello world"
# even nested
assert scope.get_instance(Foo[Foo[int]]).v.v == 100
what is not supported
- TypeVars as parameters that are not used in return type
- Typevars as injectable return type
Documentation
Container
container contains registered types, types are registered to a container via cdi.Injectable
if a type is not registered in the container, cdi will not attempt to create that type and raise an error instead, explicit is bettern then implicit
you can have multiple different container instances contaning different types, or they contain the same types but they have different providers
ctr = cdi.Container()
Forward references
some types may have unresolved forward references in their return type or parameters, when evaluated it is impossible to know what type sits behind those forward ref strings
class Foo:
# what is the `Boo` type? we just see a string
def __init__(self, boo: 'Boo') -> None: ...
such factories will not be usable for injection, to resolve forward refs
the container class provide cid.Container.update_forward_ref which takes the module you want to update the forward refs for, this takes insperation
from Pydantic/v1
the update_forward_ref has to be called after there is a class that can evaluate the forward ref name
import sys
@cdi.Injectable(ctr)
class Foo:
# references `Boo` which is not defined yet
def __init__(self, boo: 'Boo') -> None: ...
@cdi.Injectable(ctr)
class Boo: ...
# now that `Boo` is defined, we can update the factories
# in our current module
ctr.update_forward_ref(sys.modules[__name__])
# works fine
instance = Scope(__name__, container=ctr).get_instance(Foo)
Injectable
Injectable is responsible to take your type and register it into a container, the injector will create an intenal Factory for the provided type and register it into the bounded container
ctr = cdi.Container()
injector = cdi.Injectable(ctr)
injector.register(Foo)
injector.register(my_func)
it can also be used as a decorator
ctr = cdi.Container()
@cdi.Injectable(ctr)
class Foo: ...
@cdi.Injectable(ctr)
def my_func() -> int: ...
when creating the factory, the injector relys on the provided type hints
Classes
when registering a class, the dependencies are taken from the class __init__ signature, and the factory
implementation (what is called to return the type) uses the class __call__
Functions
on functions, the function signature will be used to determin the parameters and return types, calling the factory will call the provided function at the end
Constant
a constant can be injected into the container, the constant type will be the factory return type, and all scopes that require this type will evaluate to the constant, acting as a "global variable" in a container for example
ctr = cdi.Container()
cdi.Injectable().register("hello world")
scope = cdi.Scope(__name__, container=ctr)
assert scope.get_instance(str) == "hello world"
Scopes
scope defines the lifetime or bounderies of an instance, the Scope only contains the instance, and it is bounded to a cdi.Container
the Scope uses the bounded container to get factories and create instances for the types, all instances are singletones, meaning when a type is created once, it will not be created again, and the same instance will be injected
ctr = cdi.Container()
# we inject the `Foo` class into the `ctr` container
@cdi.Injectable(ctr)
class Foo:
def __init__(self, number: int) -> None:
self.number = number
cdi.Injectable(ctr).register(100)
# we define an instance scope that has access to the injectable
# registered in `ctr`
scope = cdi.Scope(__name__, container=ctr)
instance = scope.get_instance(Foo)
instance2 = scope.get_instance(Foo)
# the `Foo` will be evaluated only once and be reused
# for future calls
assert instance is instance2
assert instance.number == 100
scope2 = Scope(__name__ + '2', container=ctr)
scope2_instance = scope.get_instance(Foo)
# a different scopes don't have access to each other instances
# although they are using the same container
assert scope2_instance is not instance
inheritance
scopes can inherit parent and child like inheritance, the parent has no access to the child but the child does have access to the parent
there is no unique behavior for the child/parent scope when they aquire the relevant roles, this is mostly
for ease of use, the real inheritance comes into play via cdi.InjectableMetadata
annotation Metadata
you can change some default behaviors of the injectable type but in a way that make
sense, meaning, if you annotate str you cannot return int
types annotated with a metdata class InjectableMetadata is able to control some default behavior
of the scope
provider_scope
accepts a Callable[[Scope], Scope], this effect which scope will instantiate the annotated type
the returned scope will be used for the type instanciation
ctr = cdi.Container()
ctr2 = cdi.Container()
cdi.Injctable(ctr).register("hello world")
cdi.Injctable(ctr2).register("what?")
scope = Scope(__name__, container=ctr)
scope2 = scope.fork()
@cdi.Injectable(ctr2)
class Foo:
def __init__(
self,
value1: str,
value2: Annotated[
str,
cdi.InjectableMetadata(provider_scope=lambda scope: scope.parent) # get the str from the parent scope
]
) -> None:
self.value1 = value1
self.value2 = value2
instance = scope2.get_instance(Foo)
assert instance.value1 == "what?"
assert instance.value2 == "hello world"
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file cdi_di-0.0.1b8.tar.gz.
File metadata
- Download URL: cdi_di-0.0.1b8.tar.gz
- Upload date:
- Size: 20.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via:
uv/0.5.24
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
8b98559e09767a615b1cc38135cd96a197de30dd48b8fd9af25b7ff7bd5b7e55
|
|
| MD5 |
e246ab6b1ce484aea6da71f19fcbbdd6
|
|
| BLAKE2b-256 |
3effa8248ab7ee6c8a40bf85284ab240494e1e2d83b4f80bbb44a9cc944ee4c7
|
File details
Details for the file cdi_di-0.0.1b8-py3-none-any.whl.
File metadata
- Download URL: cdi_di-0.0.1b8-py3-none-any.whl
- Upload date:
- Size: 23.8 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via:
uv/0.5.24
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
4a5d9016c0612e46810fe3f20fe4cf66294037ded7de11a520479c1c536ea3ad
|
|
| MD5 |
97a6a8f56b18b7928c199f10e42c4a29
|
|
| BLAKE2b-256 |
7c65a8543e6e3e79d90c3c22fab2dc68fea2b0cee9b7dc7ef982f09a5022c434
|