How to use
from py3njection import inject
from some_package import ClassToInject
class Demo:
@inject
def __init__(self, object_to_use: ClassToInject):
self.dependency = object_to_use
demo = Demo()How does it work ?
The decorator @inject looks for any annotated method/function parameters (return annotation excluded).
It creates a new object from the specified class if no object is already provided.
How to install
It’s available on PyPI !
pip install py3injectionSome Notes
Unit tests come easy to set up (unless you have too many dependencies, but that would be a code smell, right ?). Juste specify mock instances at your object creation. Examples will come later.
This also means the injected object could also have some of its members injected too at their initialization !
1 maintainer
Metadata
1 maintainer
Release files for py3njection 1.1
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 |
|---|---|---|---|---|
| py3njection-1.1.tar.gz | 2.0 kB | Without provenance | Details for py3njection-1.1.tar.gz |
Release files / py3njection-1.1.tar.gz
| Download URL | py3njection-1.1.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7a6d4b2e83c906c8a1499f3531004fe2360182a7d0c2f2db6e27b689b1007bfa
|
|
BLAKE2b-256 checksum How to use checksums |
79deb1dd73121dcd37a2328f59d04e15caf063eda05a441b841cf1f489ce9854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for py3njection 1.1
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
