Update introduction docs for 2.0

This commit is contained in:
Roman Mogilatov 2016-06-03 17:33:30 +03:00
parent 5db20f0027
commit 88b563269d
2 changed files with 3 additions and 5 deletions

View File

@ -24,7 +24,7 @@ of Python objects and their dependencies in formal, pretty way.
*Dependency Injector* framework could be used in different application types: *Dependency Injector* framework could be used in different application types:
+ Web applications based on Flask, Django or any other web framework. + Web applications based on Flask, Django or any other web framework.
+ Asyncronous applications based on asyncio, Tornado and Twisted. + Asynchronous applications based on asyncio, Tornado and Twisted.
+ Standalone frameworks and libraries. + Standalone frameworks and libraries.
+ GUI applications. + GUI applications.

View File

@ -15,7 +15,7 @@ interaction between each other.
:width: 100% :width: 100%
:align: center :align: center
There are 3 main entities: providers, containers. There are 2 main entities: providers & containers.
Providers Providers
~~~~~~~~~ ~~~~~~~~~
@ -24,9 +24,7 @@ Providers are strategies of accessing objects. For example,
:py:class:`dependency_injector.providers.Factory` creates new instance :py:class:`dependency_injector.providers.Factory` creates new instance
of provided class every time it is called. of provided class every time it is called.
:py:class:`dependency_injector.providers.Singleton` creates provided :py:class:`dependency_injector.providers.Singleton` creates provided
instance once and returns it on every next call. Providers could be instance once and returns it on every next call. Base class is -
injected into each other. Providers could be overridden by another
providers. Base class is -
:py:class:`dependency_injector.providers.Provider`. :py:class:`dependency_injector.providers.Provider`.
Providers could be: Providers could be: