openstack
/
debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
95 Commits 2 Branches 63 Tags 1.6 MiB
Python 100%
Go to file
Swapnil Kulkarni (coolsvap) 279bbcaa40 Remove discover from test-requirements 
It's only needed for python < 2.7 which is not supported

Change-Id: I12d4b8ff74bdcf4586089d62a9f093d20d1fa3c4
 		2016-07-21 09:51:09 +00:00
debtcollector Fix renamed_kwarg to preserve argspec 2016-04-14 20:48:34 -05: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 Add Python 3.5 classifier and venv 2016-07-12 15:20:58 +08:00
setup.py Updated from global requirements 2015-09-17 12:11:29 +00:00
test-requirements.txt Remove discover from test-requirements 2016-07-21 09:51:09 +00:00
tox.ini Add Python 3.5 classifier and venv 2016-07-12 15:20:58 +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.