openstack/debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
133 Commits 2 Branches 63 Tags 1.6 MiB
Python 100%
0ff121e09f
Go to file
OpenStack Release Bot 0ff121e09f Update reno for stable/queens 
Change-Id: I1162de62b43895cc3bb3a70f2cf5405aebecbb6f
2018-01-24 17:59:41 +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 reno for stable/queens 2018-01-24 17:59:41 +00: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
babel.cfg 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
requirements.txt Updated from global requirements 2017-11-16 11:01:06 +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 2018-01-17 20:30:24 +00:00
tox.ini Avoid tox_install.sh for constraints support 2017-12-02 17:02:58 +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.