A collection of python patterns that help you collect your technical debt in a non-destructive manner
da416d64e2
oslotest itself depends on debtcollector and debtcollector depends on oslotest. That's a cycle dependency which makes bootstrapping the whole module chain more difficult. Instead of using oslotest, just use the standard unittest.TestCase class as base to break the dependency cycle. Change-Id: Idcbe727883fe2742d62d463bb9a195592aeaba09 |
||
---|---|---|
debtcollector | ||
doc/source | ||
releasenotes | ||
tools | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.testr.conf | ||
CONTRIBUTING.rst | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
babel.cfg | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
Debtcollector
A collection of Python deprecation patterns and strategies that help you collect your technical debt in a non-destructive manner. The goal of this library is to provide well documented developer facing deprecation patterns that start of with a basic set and can expand into a larger set of patterns as time goes on. The desired output of these patterns is to apply the warnings module to emit DeprecationWarning or PendingDeprecationWarning or similar derivative to developers using libraries (or potentially applications) about future deprecations.
- Free software: Apache license
- Documentation: http://docs.openstack.org/developer/debtcollector
- Source: http://git.openstack.org/cgit/openstack/debtcollector
- Bugs: http://bugs.launchpad.net/debtcollector