A collection of python patterns that help you collect your technical debt in a non-destructive manner
Go to file
2021-01-14 13:24:10 +00:00
debtcollector Stop to use the __future__ module. 2020-06-02 20:09:50 +02:00
doc/source Adding pre-commit 2020-09-22 10:37:04 +02:00
releasenotes Update master for stable/victoria 2020-09-11 20:55:12 +00:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:25:54 +00:00
.gitignore ignore reno generated artifacts 2020-09-22 10:39:02 +02:00
.gitreview OpenDev Migration Patch 2019-04-19 19:47:51 +00:00
.mailmap Initial commit 2014-12-12 22:26:59 -08:00
.pre-commit-config.yaml Adding pre-commit 2020-09-22 10:37:04 +02:00
.stestr.conf Switch to stestr 2018-07-09 16:15:47 +07:00
.zuul.yaml Dropping lower constraints testing 2020-12-18 15:05:57 +01:00
babel.cfg Initial commit 2014-12-12 22:26:59 -08:00
CONTRIBUTING.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
HACKING.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
LICENSE Initial commit 2014-12-12 22:26:59 -08:00
lower-constraints.txt Update lower-constraints versions 2020-06-10 10:05:45 -05:00
README.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
requirements.txt [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 10:28:51 +01:00
setup.cfg [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 10:28:51 +01:00
setup.py [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 10:28:51 +01:00
test-requirements.txt Adding pre-commit 2020-09-22 10:37:04 +02:00
tox.ini Use TOX_CONSTRAINTS_FILE 2020-11-04 10:45:57 +01:00

Team and repository tags

image

Debtcollector

Latest Version

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.