openstack/debtcollector
Code Issues Proposed changes
A collection of python patterns that help you collect your technical debt in a non-destructive manner
220 Commits 2 Branches 63 Tags 1.6 MiB
Python 100%
f49005b4e9
Go to file
Takashi Kajinami f49005b4e9 Remove Python 3.8 support 
Python 3.8 was removed from the tested runtimes for 2024.2[1] and has
not been tested since then.

[1] https://governance.openstack.org/tc/reference/runtimes/2024.2.html

Change-Id: I69d9f83c60e435b9d57e0e8dafb7f9ca4c7a898f
2024-10-24 22:28:05 +09:00
debtcollector Run pyupgrade to clean up Python 2 syntaxes 2024-10-21 19:16:02 +09:00
doc Use pre-commit hook to run doc8 2024-10-21 22:46:35 +09:00
releasenotes Remove Python 3.8 support 2024-10-24 22:28:05 +09:00
.coveragerc coveragerc: Remove non-existent path 2023-12-19 20:54:44 +09: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 Use pre-commit hook to run doc8 2024-10-21 22:46:35 +09:00
.stestr.conf Switch to stestr 2018-07-09 16:15:47 +07:00
.zuul.yaml Update CI to use unversioned jobs template 2022-03-15 15:05:43 +00: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
README.rst Replace git.openstack.org URLs with opendev.org URLs 2019-06-27 21:03:07 +08:00
requirements.txt requirements: Remove unnecessary dependency 2023-09-07 15:46:01 +01:00
setup.cfg Remove Python 3.8 support 2024-10-24 22:28:05 +09:00
setup.py [ussuri][goal] Drop python 2.7 support and testing 2020-02-04 10:28:51 +01:00
test-requirements.txt Use pre-commit hook to run doc8 2024-10-21 22:46:35 +09:00
tox.ini Use pre-commit hook to run doc8 2024-10-21 22:46:35 +09:00

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.