Manage dynamic plugins for Python applications
Go to file
Doug Hellmann 07364d43a8 move doc requirements to doc/requirements.txt
The documentation jobs now look for requirements in
doc/requirements.txt and do not use tox for release notes. Move the
dependency list from setup.cfg to the new file and update tox.ini so
the developer experience is consistent with what the CI system does.

Change-Id: I739c9eba21d1b9a680d6b0e9cc6a4cbaca56e543
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
(cherry picked from commit 3ffdb1f0ba)
2017-12-29 12:04:19 -06:00
doc move doc requirements to doc/requirements.txt 2017-12-29 12:04:19 -06:00
releasenotes switch from oslosphinx to openstackdocstheme 2017-06-28 13:09:04 -04:00
stevedore Remove oslotest from test-requirements 2017-05-23 12:11:35 +02:00
tools Add Constraints support 2016-12-21 13:39:03 +11:00
.gitignore Add reno for release notes management 2016-11-03 15:04:15 +08:00
.gitreview Update .gitreview for stable/pike 2017-07-28 21:08:45 +00:00
.testr.conf Migrate tox to use testr 2014-10-09 15:30:08 -07:00
.travis.yml Clean up Python 2.6 related stuff 2015-11-26 18:09:38 +08:00
CONTRIBUTING.rst Workflow documentation is now in infra-manual 2014-12-05 03:30:40 +00:00
LICENSE add license 2012-06-19 14:33:24 -04:00
MANIFEST.in Include all images from docs in sdist 2013-06-12 14:03:31 -04:00
README.rst Update URLs in documents according to document migration 2017-07-13 11:52:27 +08:00
announce.rst fix setuptools url 2017-06-08 16:05:52 +08:00
requirements.txt Updated from global requirements 2017-04-12 04:23:10 +00:00
setup.cfg Update URLs in documents according to document migration 2017-07-13 11:52:27 +08:00
setup.py Updated from global requirements 2017-03-02 11:56:14 +00:00
test-requirements.txt move doc requirements to doc/requirements.txt 2017-12-29 12:04:19 -06:00
tox.ini move doc requirements to doc/requirements.txt 2017-12-29 12:04:19 -06:00

README.rst

stevedore -- Manage dynamic plugins for Python applications

Latest Version

Downloads

image

Python makes loading code dynamically easy, allowing you to configure and extend your application by discovering and loading extensions ("plugins") at runtime. Many applications implement their own library for doing this, using __import__ or importlib. stevedore avoids creating yet another extension mechanism by building on top of setuptools entry points. The code for managing entry points tends to be repetitive, though, so stevedore provides manager classes for implementing common patterns for using dynamically loaded extensions.