openstack/stevedore
Code Issues Proposed changes

doc cleanup

Browse Source 
Signed-off-by: Doug Hellmann <doug.hellmann@dreamhost.com>
This commit is contained in:
Doug Hellmann 2013-06-05 18:48:40 -04:00
parent c40941e741
commit 9065ff5623
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
docs/source/history.rst
View File

@ -15,6 +15,7 @@ dev
- Add ``__getitem__`` to
:class:`~stevedore.extension.ExtensionManager` for looking up
individual plugins by name (:issue:`15`).
- Start working on the tutorial, :doc:`tutorial/index`.
0.8

13
docs/source/tutorial/loading.rst
View File

@ -2,17 +2,16 @@
Loading the Plugins
=====================
Load plugins using stevedore is as easy as creating them. There are
several different enabling and invocation patterns to choose from,
depending on your needs.
There are several different enabling and invocation patterns for
consumers of plugins, depending on your needs.
Loading Drivers
===============
The most common way plugins are used is as individual drivers. There
may be many plugin options to choose from, but only one needs to be
loaded and called. The :class:`~stevedore.driver.DriverManager` class
supports this pattern.
The most common way plugins are used is as individual drivers. In this
case, there may be many plugin options to choose from, but only one
needs to be loaded and called. The
:class:`~stevedore.driver.DriverManager` class supports this pattern.
This example program uses a :class:`DriverManager` to load a formatter
defined in the examples for stevedore. It then uses the formatter to