Merge branch 'release/3.30.0' into master

Author: rmk135

README.rst

@@ -157,6 +157,7 @@ Choose one of the following:
 - `Flask web application tutorial <http://python-dependency-injector.ets-labs.org/tutorials/flask.html>`_
 - `Aiohttp REST API tutorial <http://python-dependency-injector.ets-labs.org/tutorials/aiohttp.html>`_
 - `Asyncio monitoring daemon tutorial <http://python-dependency-injector.ets-labs.org/tutorials/asyncio-daemon.html>`_
+- `CLI application tutorial <http://python-dependency-injector.ets-labs.org/tutorials/cli.html>`_
 
 Installation
 ============

docs/examples/index.rst

@@ -15,7 +15,6 @@ and powered by *Dependency Injector* framework.
 ..  toctree::
     :maxdepth: 2
 
-    movie_lister
     services_miniapp_v1
     services_miniapp_v2
     bundles_miniapp

docs/examples/movie_lister.rst

@@ -135,8 +135,9 @@ Choose one of the following as a next step:
     + :ref:`flask-tutorial`
     + :ref:`aiohttp-tutorial`
     + :ref:`asyncio-daemon-tutorial`
-+ Know more about the :ref:`providers`.
-+ Go to the :ref:`contents`.
+    + :ref:`cli-tutorial`
++ Know more about the :ref:`providers`
++ Go to the :ref:`contents`
 
 Useful links
 ~~~~~~~~~~~~

docs/images/miniapps/movie_lister/classes.png

@@ -7,6 +7,13 @@ that were made in every particular version.
 From version 0.7.6 *Dependency Injector* framework strictly 
 follows `Semantic versioning`_
 
+3.30.0
+------
+- Rework ``Movie Lister`` example.
+- Add tutorial for building ``Movie Lister``.
+- Make some rewording for the other tutorials.
+- Fix a couple of typos.
+
 3.29.0
 ------
 - Update README with the more direct message on what is ``Dependency Injector`` and how is it

docs/introduction/di_in_python.rst

@@ -1,3 +1,5 @@
+.. _selector-provider:
+
 Selector providers
 ------------------
 

docs/main/changelog.rst

@@ -922,7 +922,7 @@ We've used the ``Dependency Injector`` as a dependency injection framework.
 
 The benefit you get with the ``Dependency Injector`` is the container. It starts to payoff
 when you need to understand or change your application structure. It's easy with the container,
-cause you have everything in one place:
+cause you have everything defined explicitly in one place:
 
 .. code-block:: python
 
@@ -962,8 +962,8 @@ cause you have everything in one place:
 
 What's next?
 
-- Look at the other :ref:`tutorials`.
-- Know more about the :ref:`providers`.
-- Go to the :ref:`contents`.
+- Look at the other :ref:`tutorials`
+- Know more about the :ref:`providers`
+- Go to the :ref:`contents`
 
 .. disqus::

docs/providers/selector.rst

@@ -1030,7 +1030,7 @@ We've used the ``Dependency Injector`` as a dependency injection framework.
 
 The benefit you get with the ``Dependency Injector`` is the container. It starts to payoff
 when you need to understand or change your application structure. It's easy with the container,
-cause you have everything in one place:
+cause you have everything defined explicitly in one place:
 
 .. code-block:: python
 
@@ -1080,8 +1080,8 @@ cause you have everything in one place:
 
 What's next?
 
-- Look at the other :ref:`tutorials`.
-- Know more about the :ref:`providers`.
-- Go to the :ref:`contents`.
+- Look at the other :ref:`tutorials`
+- Know more about the :ref:`providers`
+- Go to the :ref:`contents`
 
 .. disqus::