openstack/debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
101 Commits 2 Branches 63 Tags 1.6 MiB
Python 100%
a3d122843b
Go to file
ChangBo Guo(gcb) a3d122843b Trivial: Remove 'MANIFEST.in' 
Everything in this file is automatically generated by pbr[1].
There appears to be no good reason to keep it around.
Note: we don't generate a MANIFEST.in in a file format from pbr,
but as input for setuptools.setup()

[1]https://github.com/openstack-dev/pbr/blob/master/pbr/packaging.py#L454

Change-Id: Ib26e99d64c0afb59f23c566201c465b6b99c5c7d
2016-11-01 15:19:58 +08:00
debtcollector Fix a typo in comment 2016-08-26 13:42:51 +02: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
babel.cfg 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 tweak language in readme 2015-09-24 20:33:28 +00:00
requirements.txt Drop babel as requirement since its not used 2016-04-20 18:52:53 -07: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 2016-10-22 01:18:15 +00:00
tox.ini Drop *openstack/common* in flake8 exclude list 2016-08-02 20:10:29 +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.