IOCynergy
Python module for IOC container using dependency injection (uses python 3+ type hints, supported until Python3.7)
Easy way to initialize your services
from cynergy import container
class TestClass:
pass
class ParentClass:
def __init__(self, test_class: TestClass):
self.test_class = test_class
instance = container.get(ParentClass) # Returns TestClass initialized as singleton
print(type(instance)) # ParentClass
print(type(instance.test_class)) # TestClass
Access to your configuration from any service
from cynergy import container
from cynergy.config import Config, MemoryConfig
from cynergy.attributes import arguments
@arguments(db=Config('db_name'),host=Config('hostname'))
class DbConnector:
def __init__(self, db: str, host: str):
self.db = db
self.host = host
container.initialize(MemoryConfig({
"db_name": "LocalDbName",
"hostname": "localhost"
}))
instance = container.get(DbConnector)
print(instance.db) # LocalDbName
print(instance.host) # localhost
** You can implement your own configuration provider (for exmaple you can create DbConfigProvider which provides your settings from the db)
Manually register special types
from cynergy import container
class Original:
pass
class Other:
pass
container.register_class(Original, Other)
instance = container.get(Original)
print(type(instance)) # Other
Register collection of services
from typing import List
from cynergy import container
class HandlerBase:
pass
class SomeHandler1(HandlerBase):
pass
class SomeHandler2(HandlerBase):
pass
class SomeService:
def __init__(self, handlers: List[HandlerBase]):
self.handlers = handlers
container.register_many(HandlerBase, [SomeHandler1, SomeHandler2])
instance = container.get(SomeService)
print(type(instance.handlers)) # list
print(type(instance.handlers[0])) # SomeHandler1
print(type(instance.handlers[1])) # SomeHandler2
Metadata
Release files for cynergy 1.2.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 |
|---|---|---|---|---|
| cynergy-1.2.0.tar.gz | 7.3 kB | Without provenance | Details for cynergy-1.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cynergy-1.2.0-py3-none-any.whl | Python 3 | none | any | Details for cynergy-1.2.0-py3-none-any.whl |
Total release size: 14.6 kB
Release files / cynergy-1.2.0.tar.gz
| Download URL | cynergy-1.2.0.tar.gz |
|---|---|
| Size | 7.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eda11957e6f0690c700a9c0057f4921b4aceea136038d3d0217d3c180aa5deca
|
|
BLAKE2b-256 checksum How to use checksums |
94be78b52c95dfafa30fd21dabd651a457aa0274d408fc7a63ffeb850d5bfc88
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.0
|
Release files / cynergy-1.2.0-py3-none-any.whl
| Download URL | cynergy-1.2.0-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3517dd78e4baea3638a893765aef97e1039b1348b7b49adcf14748d6dbe38b1e
|
|
BLAKE2b-256 checksum How to use checksums |
4467f0b35b46100b20f7d947eac5e7c9573c82d1f349efbe62d2ccd460127810
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.4.0 requests-toolbelt/0.9.1 tqdm/4.36.1 CPython/3.6.0
|
Security for cynergy 1.2.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.
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.