A collection of python patterns that help you collect your technical debt in a non-destructive manner
Go to file
Thomas Bechtold da416d64e2 Do not require oslotest for testing
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
2017-05-22 17:04:30 +02:00
debtcollector Do not require oslotest for testing 2017-05-22 17:04:30 +02:00
doc/source Typo fix for module debtcollector 2016-11-07 15:27:58 +08:00
releasenotes Update reno for stable/ocata 2017-01-20 19:15:01 +00:00
tools Add Constraints support 2016-12-20 15:41:19 +11:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:25:54 +00:00
.gitignore Add reno for release notes management 2016-11-01 15:52:47 +08:00
.gitreview Add a .gitreview file with correct values 2015-01-20 10:33:53 -08:00
.mailmap Initial commit 2014-12-12 22:26:59 -08:00
.testr.conf Initial commit 2014-12-12 22:26:59 -08:00
CONTRIBUTING.rst Initial commit 2014-12-12 22:26:59 -08:00
HACKING.rst Initial commit 2014-12-12 22:26:59 -08:00
LICENSE Initial commit 2014-12-12 22:26:59 -08:00
README.rst Show team and repo badges on README 2016-11-25 13:16:44 +01:00
babel.cfg Initial commit 2014-12-12 22:26:59 -08:00
requirements.txt Updated from global requirements 2017-04-12 04:10:39 +00:00
setup.cfg Python 3.4 support has been removed 2017-03-07 17:45:42 +05:30
setup.py Updated from global requirements 2017-03-02 11:43:37 +00:00
test-requirements.txt Do not require oslotest for testing 2017-05-22 17:04:30 +02:00
tox.ini Python 3.4 support has been removed 2017-03-07 17:45:42 +05:30

README.rst

Team and repository tags

image

Debtcollector

Latest Version

Downloads

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.