| --- | :---: | :---: | :---: | :---: | :---: |
| Master | [](https://travis-ci.org/DrTexxOfficial/dbi) | [](https://codecov.io/gh/DrTexxOfficial/dbi) | [](https://requires.io/github/DrTexxOfficial/dbi/requirements/?branch=master) | [](https://GitHub.com/DrTexxOfficial/dbi/issues/) | [](https://GitHub.com/DrTexxOfficial/dbi/pull/) |
| Develop | [](https://travis-ci.org/DrTexxOfficial/dbi) | [](https://codecov.io/gh/DrTexxOfficial/dbi) | [](https://requires.io/github/DrTexxOfficial/dbi/requirements/?branch=develop)
# Debug Interface - DBI
[](https://pypi.python.org/pypi/dbi/)
[](https://GitHub.com/DrTexxOfficial/dbi/releases/)
[](https://github.com/DrTexxOfficial/dbi/blob/master/LICENSE)
[](https://GitHub.com/DrTexxOfficial/dbi/releases/)
<img src="docs/dbi_logo.png" alt="dbi logo" width="200"/>
## Installation
### Install via pip
Install as user (recommended):
$ pip3 install dbi --user
Install as root:
$ sudo pip3 install dbi
### Install from source
Clone this repository:
$ git clone https://github.com/DrTexxOfficial/dbi.git
Install requirements:
$ cd dbi
$ pip3 install -r requirements.txt --user
## Script Functionality
### User-Written Verbosity-Dependant Debug Messages
- information is only show when A and B are satisfied
- debugging is active
- the threshold verbosity is reached or exceeded (this threshold is specified on a per-message basis)
- verbosity can be
- set in advanced
- **modified on-the-fly**
- multiple **external functions** can be executed in a single-line
- users can write their own debugging messages on the status of each function's progress
- console output is colour-coded (based on verbosity levels)
## What is the purpose?
My console had become populated by indecernable walls of debugging text, all thanks to riddling my scripts with lines like `print(str(var),var)` for debugging.
So I created a module to maintain my sanity and save my time.
## Examples
Initial config:
```python3
from dbi import Dbi
dbi = Dbi(3,True)
dpm = dbi.print_message
```
Generic example:
```
[IN ]: dpm(2,"message with","sub-message")
[OUT]: [3][2]<=[2018-12-10 01:54:59.845995] message with | sub-message
```
<br/>
[](https://www.python.org/)
Metadata
Release files for qwerty 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| qwerty-1.2.1-py3-none-any.whl | Python 3 | none | any | Details for qwerty-1.2.1-py3-none-any.whl |
Release files / qwerty-1.2.1-py3-none-any.whl
| Download URL | qwerty-1.2.1-py3-none-any.whl |
|---|---|
| Size | 16.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1c4fb637143b636c3e87572771c66ef6f67f0b7fc0e207276f24db878ffef5b
|
|
BLAKE2b-256 checksum How to use checksums |
74eac5864cc4d928b7c52df2ab341acfd53f6c26c5b287abed4c780ddc96ed52
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.8.1 pkginfo/1.2.1 requests/2.20.1 setuptools/40.6.2 requests-toolbelt/0.7.0 clint/0.5.1 CPython/3.5.3 Linux/4.9.0-8-amd64
|
Security for qwerty 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.