07364d43a8
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
|
||
---|---|---|
doc | ||
releasenotes | ||
stevedore | ||
tools | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
.travis.yml | ||
CONTRIBUTING.rst | ||
LICENSE | ||
MANIFEST.in | ||
README.rst | ||
announce.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
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