openstack
/
debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
109 Commits 2 Branches 63 Tags 1.6 MiB
Python 100%
Go to file
OpenStack Proposal Bot d1ac903c11 Updated from global requirements 
Change-Id: Ia366a95bcbd37a0dcea11cdf7c1567ae08ab06aa
 		2017-02-10 05:47:50 +00:00
debtcollector Fix a typo in comment 2016-08-26 13:42:51 +02:00
doc/source Typo fix for module debtcollector 2016-11-07 15:27:58 +08:00
releasenotes Add reno for release notes management 2016-11-01 15:52:47 +08: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 2016-11-09 04:14:45 +00:00
setup.cfg Update homepage with developer documentation page 2016-09-24 14:25:48 +08:00
setup.py Updated from global requirements 2015-09-17 12:11:29 +00:00
test-requirements.txt Updated from global requirements 2017-02-10 05:47:50 +00:00
tox.ini Add Constraints support 2016-12-20 15:41:19 +11: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.