ets-labs/python-dependency-injector
1
1
Fork 0
mirror of https://github.com/ets-labs/python-dependency-injector.git synced 2025-10-31 07:57:43 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update README.rst

Browse Source
This commit is contained in:
Roman Mogylatov 2020-08-10 21:44:58 -04:00 committed by GitHub
parent 408ba1e66c
commit 0401488587
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.rst
View File

@ -57,12 +57,12 @@ The power of the framework is in its simplicity and straightforwardness.
It stands on two principles: It stands on two principles:
- Explicit is better than implicit (PEP20). - Explicit is better than implicit (PEP20).
- Do NOT pollute your application code. - Do no magic to your code.
How does it different from the other frameworks? How does it different from the other frameworks?
- **No autowiring.** The framework does NOT do any autowiring / autoresolving of the dependencies. You need to specify everything explicitly. Because *"Explicit is better than implicit" (PEP20)*. - **No autowiring.** The framework does NOT do any autowiring / autoresolving of the dependencies. You need to specify everything explicitly. Because *"Explicit is better than implicit" (PEP20)*.
- **Your code does not know about the Dependency Injector** .Your application does NOT depend on the framework. No ``@inject`` decorators, annotations, patching or any other magic tricks. - **Does not pollute your code** .Your application does NOT know and does NOT depend on the framework. No ``@inject`` decorators, annotations, patching or any other magic tricks.
``Dependency Injector`` follows a simple contract with you: ``Dependency Injector`` follows a simple contract with you: