Manage dynamic plugins for Python applications
a4af200a42
This is a mechanically generated patch to add a unit test job running under Python 3.6 as part of the python3-first goal. See the python3-first goal document for details: https://governance.openstack.org/tc/goals/stein/python3-first.html Change-Id: I48e460abaf97613dfd2c9b035b322d38ba9bab52 Story: #2002586 Task: #24322 |
||
---|---|---|
doc | ||
releasenotes | ||
stevedore | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.travis.yml | ||
.zuul.yaml | ||
announce.rst | ||
CONTRIBUTING.rst | ||
LICENSE | ||
lower-constraints.txt | ||
MANIFEST.in | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
stevedore -- Manage dynamic plugins for Python applications
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.
- Free software: Apache license
- Documentation: https://docs.openstack.org/stevedore/latest
- Source: https://git.openstack.org/cgit/openstack/stevedore
- Bugs: https://bugs.launchpad.net/python-stevedore