openstack
/
debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
87 Commits 2 Branches 63 Tags 1.5 MiB
Python 100%
Go to file
Joshua Harlow c204667ed8 Drop babel as requirement since its not used 
See the following thread for more details.

http://lists.openstack.org/pipermail/openstack-dev/2016-April/thread.html#92510

Change-Id: I2b91808ad27de93bf28701fcd2fc8e038c4573d1
 		2016-04-20 18:52:53 -07:00
debtcollector Add updated_kwarg_default_value decorator 2016-01-07 14:36:52 +00:00
doc/source Add updated_kwarg_default_value decorator 2016-01-07 14:36:52 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:25:54 +00:00
.gitignore Add updated_kwarg_default_value decorator 2016-01-07 14:36:52 +00: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
MANIFEST.in Initial commit 2014-12-12 22:26:59 -08:00
README.rst tweak language in readme 2015-09-24 20:33:28 +00:00
babel.cfg Initial commit 2014-12-12 22:26:59 -08:00
requirements.txt Drop babel as requirement since its not used 2016-04-20 18:52:53 -07:00
setup.cfg Remove Python 2.6 classifier 2015-11-17 16:26:36 +08:00
setup.py Updated from global requirements 2015-09-17 12:11:29 +00:00
test-requirements.txt Updated from global requirements 2016-04-08 00:26:07 +00:00
tox.ini Add debug testenv in tox 2016-01-13 14:13:00 +08:00

README.rst

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.