From 408ba1e66ce48e17afb9d0aed3f6c5ce52b987d2 Mon Sep 17 00:00:00 2001 From: Roman Mogylatov Date: Mon, 10 Aug 2020 21:43:30 -0400 Subject: [PATCH] Update README.rst --- README.rst | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/README.rst b/README.rst index 4968d02f..9a427605 100644 --- a/README.rst +++ b/README.rst @@ -56,13 +56,18 @@ The power of the framework is in its simplicity and straightforwardness. It stands on two principles: - - Explicit is better than implicit (PEP20). - - Do NOT pollute your application code. +- Explicit is better than implicit (PEP20). +- Do NOT pollute your application code. How does it different from the other frameworks? -- 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 application code does NOT know about the framework and does NOT depend on it. No ``@inject`` decorators, annotations, patching or any other magic tricks. +- **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. + +``Dependency Injector`` follows a simple contract with you: + +- You tell the framework how to build you code +- The framework does it for you ``Dependency Injector`` is a simple tool for the powerful concept.