openstack
/
debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
205 Commits
7 Branches
10 Tags
1.5 MiB
 
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
Hervé Beraud e44ad1df84
Drop python3.6/3.7 support in testing runtime 		4 months ago
debtcollector Remove references to Python 2 objects 6 months ago
doc/source Remove unnecessary 'coding' lines 10 months ago
releasenotes Remove unnecessary 'coding' lines 10 months ago
.coveragerc Change ignore-errors to ignore_errors 7 years ago
.gitignore ignore reno generated artifacts 2 years ago
.gitreview OpenDev Migration Patch 3 years ago
.mailmap Initial commit 8 years ago
.pre-commit-config.yaml Move flake8 as a pre-commit local target. 1 year ago
.stestr.conf Switch to stestr 4 years ago
.zuul.yaml Update CI to use unversioned jobs template 5 months ago
CONTRIBUTING.rst Replace git.openstack.org URLs with opendev.org URLs 3 years ago
HACKING.rst Replace git.openstack.org URLs with opendev.org URLs 3 years ago
LICENSE Initial commit 8 years ago
README.rst Replace git.openstack.org URLs with opendev.org URLs 3 years ago
babel.cfg Initial commit 8 years ago
requirements.txt requirements: Remove pbr 9 months ago
setup.cfg Drop python3.6/3.7 support in testing runtime 4 months ago
setup.py [ussuri][goal] Drop python 2.7 support and testing 3 years ago
test-requirements.txt Adding pre-commit 2 years ago
tox.ini Remove lower-constraints remnants 2 years ago

README.rst

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.