mirror of
https://github.com/ets-labs/python-dependency-injector.git
synced 2025-07-09 15:42:23 +03:00
Update key features list and key features page in docs
This commit is contained in:
parent
8444d7d1d5
commit
6b1dd3aef6
18
README.rst
18
README.rst
|
@ -3,18 +3,18 @@ Dependency Injector - Python dependency injection framework
|
||||||
===========================================================
|
===========================================================
|
||||||
|
|
||||||
*Dependency Injector* is a Python dependency injection framework. It was
|
*Dependency Injector* is a Python dependency injection framework. It was
|
||||||
designed to be unified, developer's friendly tool for managing any kind
|
designed to be unified, developer-friendly tool for managing any kind
|
||||||
of Python objects and their dependencies in formal, pretty way.
|
of Python objects and their dependencies in formal, pretty way.
|
||||||
|
|
||||||
Below is a list of some key features and points of *Dependency Injector*:
|
*Dependency Injector* framework key features are:
|
||||||
|
|
||||||
- Easy, smart, pythonic style.
|
+ Easy, smart, pythonic style.
|
||||||
- Obvious, clear structure.
|
+ Obvious, clear structure.
|
||||||
- Memory efficiency.
|
+ Extensibility and flexibility.
|
||||||
- Thread safety.
|
+ Memory efficiency.
|
||||||
- Semantic versioning.
|
+ Thread safety.
|
||||||
|
+ Documentation.
|
||||||
Main idea of *Dependency Injector* is to keep dependencies under control.
|
+ Semantic versioning.
|
||||||
|
|
||||||
Status
|
Status
|
||||||
------
|
------
|
||||||
|
|
|
@ -10,16 +10,18 @@ Dependency Injector --- Python dependency injection framework
|
||||||
their dependencies in formal, pretty way.
|
their dependencies in formal, pretty way.
|
||||||
|
|
||||||
*Dependency Injector* is a Python dependency injection framework. It was
|
*Dependency Injector* is a Python dependency injection framework. It was
|
||||||
designed to be unified, developer's friendly tool for managing any kind
|
designed to be unified, developer-friendly tool for managing any kind
|
||||||
of Python objects and their dependencies in formal, pretty way.
|
of Python objects and their dependencies in formal, pretty way.
|
||||||
|
|
||||||
Key features of *Dependency Injector*:
|
*Dependency Injector* framework key features are:
|
||||||
|
|
||||||
- Easy, smart, pythonic style.
|
+ Easy, smart, pythonic style.
|
||||||
- Obvious, clear structure.
|
+ Obvious, clear structure.
|
||||||
- Memory efficiency.
|
+ Extensibility and flexibility.
|
||||||
- Thread safety.
|
+ Memory efficiency.
|
||||||
- Semantic versioning.
|
+ Thread safety.
|
||||||
|
+ Documentation.
|
||||||
|
+ Semantic versioning.
|
||||||
|
|
||||||
Status
|
Status
|
||||||
------
|
------
|
||||||
|
|
|
@ -1,2 +1,39 @@
|
||||||
Key features of Dependency Injector
|
Key features of Dependency Injector
|
||||||
-----------------------------------
|
-----------------------------------
|
||||||
|
|
||||||
|
*Dependency Injector* is a dependency injection framework for Python projects.
|
||||||
|
It was designed to be unified, developer-friendly tool for managing any kind
|
||||||
|
of Python objects and their dependencies in formal, pretty way.
|
||||||
|
|
||||||
|
*Dependency Injector* framework key features are:
|
||||||
|
|
||||||
|
+ Easy, smart, pythonic style.
|
||||||
|
+ Obvious, clear structure.
|
||||||
|
+ Extensibility and flexibility.
|
||||||
|
+ Memory efficiency.
|
||||||
|
+ Thread safety.
|
||||||
|
+ Documentation.
|
||||||
|
+ Semantic versioning.
|
||||||
|
|
||||||
|
*Dependency Injector* framework could be used in different application types:
|
||||||
|
|
||||||
|
+ Web applications based on Flask, Django or any other web framework.
|
||||||
|
+ Asyncronous applications based on asyncio, Tornado and Twisted.
|
||||||
|
+ Standalone frameworks and libraries.
|
||||||
|
+ GUI applications.
|
||||||
|
|
||||||
|
*Dependency Injector* framework could be integrated on different project
|
||||||
|
stages:
|
||||||
|
|
||||||
|
+ It could be used in the beginning of development of new applications.
|
||||||
|
+ It could be integrated into applications that are in active development
|
||||||
|
stage.
|
||||||
|
+ It could be used for refactoring of legacy applications.
|
||||||
|
|
||||||
|
Components of *Dependency Injector* framework could be used:
|
||||||
|
|
||||||
|
+ In composition with each other.
|
||||||
|
+ Separately between each other.
|
||||||
|
|
||||||
|
Main idea of *Dependency Injector* framework is to be useful tool for the
|
||||||
|
right thing.
|
||||||
|
|
Loading…
Reference in New Issue
Block a user