Fix module API references in docs

This commit is contained in:
Roman Mogilatov 2015-11-29 23:30:48 +02:00
parent e309425ee5
commit baa1a86cfe
12 changed files with 12 additions and 12 deletions

View File

@ -7,7 +7,7 @@ Current section of documentation describes advanced usage of
@inject decorator
-----------------
.. module:: dependency_injector.injections
.. currentmodule:: dependency_injector.injections
:py:func:`inject` decorator is a part of
:py:mod:`dependency_injector.injections` module.

View File

@ -1,7 +1,7 @@
Catalog provider bundles
------------------------
.. module:: dependency_injector.catalogs
.. currentmodule:: dependency_injector.catalogs
:py:class:`CatalogBundle` is a frozen, limited collection of catalog
providers. While catalog could be used as a centralized place for

View File

@ -1,7 +1,7 @@
Declarative catalogs
--------------------
.. module:: dependency_injector.catalogs
.. currentmodule:: dependency_injector.catalogs
:py:class:`DeclarativeCatalog` is a catalog of providers that could be
defined in declarative manner. It should cover most of the cases when list

View File

@ -1,7 +1,7 @@
Dynamic catalogs
----------------
.. module:: dependency_injector.catalogs
.. currentmodule:: dependency_injector.catalogs
:py:class:`DynamicCatalog` is a catalog of providers that could be created in
application's runtime. It should cover most of the cases when list of

View File

@ -1,7 +1,7 @@
Overriding of catalogs
----------------------
.. module:: dependency_injector.catalogs
.. currentmodule:: dependency_injector.catalogs
Catalogs can be overridden by other catalogs. This, actually, means that
all of the providers from overriding catalog will override providers with the

View File

@ -1,7 +1,7 @@
Callable providers
------------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
:py:class:`Callable` provider is a provider that wraps particular callable with
some injections. Every call of this provider returns result of call of initial

View File

@ -1,7 +1,7 @@
Writing of custom providers
---------------------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
List of *Dependency Injector* providers could be widened with custom providers.

View File

@ -1,7 +1,7 @@
External dependency providers
-----------------------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
:py:class:`ExternalDependency` provider can be useful for development of
self-sufficient libraries / modules / applications that has required external

View File

@ -1,7 +1,7 @@
Factory providers
-----------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
:py:class:`Factory` provider creates new instance of specified class on every
call.

View File

@ -1,7 +1,7 @@
Overriding of providers
-----------------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
Every provider could be overridden by another provider.

View File

@ -1,7 +1,7 @@
Singleton providers
-------------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
:py:class:`Singleton` provider creates new instance of specified class on
first call and returns same instance on every next call.

View File

@ -1,7 +1,7 @@
Static providers
----------------
.. module:: dependency_injector.providers
.. currentmodule:: dependency_injector.providers
Static providers are family of providers that return their values "as is".
There are four types of static providers: