ets-labs/python-dependency-injector
1
1
Fork 0
mirror of https://github.com/ets-labs/python-dependency-injector.git synced 2025-02-16 19:40:59 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update docs index and key features page

Browse Source
This commit is contained in:
Roman Mogylatov 2020-08-10 22:29:25 -04:00
parent 1c189c47e2
commit bb1403b5e9
2 changed files with 33 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs/index.rst
View File

@ -64,7 +64,22 @@ Dependency Injector --- Dependency injection framework for Python
``Dependency Injector`` is a dependency injection framework for Python. ``Dependency Injector`` is a dependency injection framework for Python.
It helps you understand and change the structure of the application. It stands on two principles:
- Explicit is better than implicit (PEP20).
- Do no magic to your code.
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)*.
- **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`` makes a simple contract with you:
- You tell the framework how to build you code
- The framework does it for you
The power of the ``Dependency Injector`` is in its simplicity and straightforwardness. It is a simple tool for the powerful concept.
With the ``Dependency Injector`` you keep **application structure in one place**. With the ``Dependency Injector`` you keep **application structure in one place**.
This place is called **the container**. You use the container to manage all the components of the This place is called **the container**. You use the container to manage all the components of the

17
docs/introduction/key_features.rst
View File

@ -13,6 +13,23 @@ It was designed to be a unified and developer-friendly tool that helps
implement a dependency injection design pattern in a formal, pretty, and implement a dependency injection design pattern in a formal, pretty, and
Pythonic way. Pythonic way.
It stands on two principles:
- Explicit is better than implicit (PEP20).
- Do no magic to your code.
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)*.
- **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`` makes a simple contract with you:
- You tell the framework how to build you code
- The framework does it for you
The power of the ``Dependency Injector`` is in its simplicity and straightforwardness. It is a simple tool for the powerful concept.
The key features of the ``Dependency Injector`` framework are: The key features of the ``Dependency Injector`` framework are:
+ Easy, smart, and Pythonic style. + Easy, smart, and Pythonic style.