ashka-lifecycle
ashka-lifecycle adds an application bootstrap phase to dishka containers. Dependencies
registered with AshkaScope.BOOTSTRAP are created eagerly when the root
container is initialized, while retaining the dependency, caching, and
shutdown behavior of dishka's Scope.APP. Both synchronous and asynchronous
containers support explicit initialization and initialization through their
context managers.
The implementation is designed to keep the integration with dishka minimally
intrusive. ashka-lifecycle extends the public provider and container construction APIs,
while leaving dishka's scope and factory implementations unchanged. The
AshkaScope.BOOTSTRAP value is only an ashka-side marker; the provider maps it
to dishka's native Scope.APP instead of introducing a new dishka scope.
ashka-lifecycle maintains its own registry of Bootstrap provider sources and the corresponding dependency keys for each container. When a container is entered, ashka-lifecycle looks up the registered keys and eagerly resolves them using the existing container API. Synchronous containers resolve them one by one, while asynchronous containers resolve them concurrently. This keeps the changes localized to the public extension points and leaves dishka's existing scope, caching, shutdown, and factory behavior in control.
ashka-lifecycle can also be installed and used independently from ashka as
an escape hatch. In this mode, manually import ashka_lifecycle and manually call ashka_lifecycle.activate_lifecycle() before
importing dishka to ensure that its patches are applied.
See more details and about how to use:
1 maintainer
Metadata
1 maintainer
Release files for ashka-lifecycle 1.0.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 | |
|---|---|---|---|
| ashka_lifecycle-1.0.0.tar.gz | 4.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ashka_lifecycle-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.8 kB
Release files / ashka_lifecycle-1.0.0.tar.gz
| Download URL | ashka_lifecycle-1.0.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71a6d17ec1683f3fb65500f90002179fdf31abe49ad77d18a5066d5e845aae65
|
|
BLAKE2b-256 checksum How to use checksums |
84bb108a08d49bdef29091cc7e2f71bef73d5a2efb41b9b350c4aebf101e51a2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency logRelease files / ashka_lifecycle-1.0.0-py3-none-any.whl
| Download URL | ashka_lifecycle-1.0.0-py3-none-any.whl |
|---|---|
| Size | 7.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8cbeea3fdb0d967887382971cb56704e2726409593edf4c306c1771683b02f64
|
|
BLAKE2b-256 checksum How to use checksums |
26a9af0a77306ee1cace36b44f51464d92a499725e9a51617bf3965b86812233
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 17, 2026.
Transparency log
