openstack
/
debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
169 Commits 2 Branches 63 Tags 1.6 MiB
Python 100%
Go to file
Zuul 0be4911f90 Merge "Add Python 3 Train unit tests" 2019-07-16 22:36:25 +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 Update master for stable/stein 2019-03-18 14:38:50 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:25:54 +00:00
.gitignore Switch to stestr 2018-07-09 16:15:47 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:47:51 +00:00
.mailmap Initial commit 2014-12-12 22:26:59 -08:00
.stestr.conf Switch to stestr 2018-07-09 16:15:47 +07:00
.zuul.yaml Add Python 3 Train unit tests 2019-07-05 14:39:10 -04:00
CONTRIBUTING.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
HACKING.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
LICENSE Initial commit 2014-12-12 22:26:59 -08:00
README.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
babel.cfg Initial commit 2014-12-12 22:26:59 -08:00
lower-constraints.txt Switch to stestr 2018-07-09 16:15:47 +07:00
requirements.txt Updated from global requirements 2017-11-16 11:01:06 +00:00
setup.cfg Add Python 3 Train unit tests 2019-07-05 14:39:10 -04:00
setup.py Updated from global requirements 2017-03-02 11:43:37 +00:00
test-requirements.txt Update Sphinx requirement 2019-05-16 15:32:05 +02:00
tox.ini Merge "Add Python 3 Train unit tests" 2019-07-16 22:36:25 +00:00

README.rst

Team and repository tags

image

Debtcollector

Latest Version

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.