A collection of python patterns that help you collect your technical debt in a non-destructive manner
Go to file
OpenStack Proposal Bot 28d2552da9 Updated from global requirements
Change-Id: I5288c2f8b3b70bab0b45aab76de7a6f38f352916
2017-08-11 18:57:43 +00:00
debtcollector Do not require oslotest for testing 2017-05-22 17:04:30 +02:00
doc/source rearrange existing documentation to fit the new standard layout 2017-07-01 19:00:17 +09:00
releasenotes rearrange existing documentation to fit the new standard layout 2017-07-01 19:00:17 +09: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 Update .gitreview for stable/pike 2017-07-28 21:03:03 +00: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 rearrange existing documentation to fit the new standard layout 2017-07-01 19:00:17 +09:00
HACKING.rst Update URLs in documents according to document migration 2017-07-12 19:27:03 +08:00
LICENSE Initial commit 2014-12-12 22:26:59 -08:00
README.rst Update URLs in documents according to document migration 2017-07-12 19:27:03 +08: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 Update URLs in documents according to document migration 2017-07-12 19:27:03 +08:00
setup.py Updated from global requirements 2017-03-02 11:43:37 +00:00
test-requirements.txt Updated from global requirements 2017-08-11 18:57:43 +00:00
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/pike 2017-07-28 21:03:05 +00:00

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.