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-07-07 16:08:19 -04:00 committed by GitHub
parent cf2b113b25
commit 293fc3217f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.rst
View File

@ -48,7 +48,7 @@ Why do I need it?
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 application. All the component dependencies are defined explicitly. This provides the control on the application structure. It is **easy to understand and change** it. This place is called **the container**. You use the container to manage all the components of the application. All the component dependencies are defined explicitly. This provides the control on the application structure. It is **easy to understand and change** it.
.. figure:: ./di-map4.svg .. figure:: ./di-map5.svg
*The container is like a map of your application. You always know what depends on what.* *The container is like a map of your application. You always know what depends on what.*