Manage dynamic plugins for Python applications
64f70f245a
The pyNN factors automatically set basepython unless explicitly requested otherwise. Therefore, "testenv:py27" section are unnecessary and should be removed as the recommendation from Stephen in [1] [1] https://review.openstack.org/#/c/580250/3/tox.ini@15 Change-Id: I07428041f70c68520c451589fc65cb586741b69b |
||
---|---|---|
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