<pre>
<h1>defiance</h1>
<h2>description</h2>
This is a module that can reliably
ascertain the health status of software.
(It's like a testing kit)
<h2>install</h2>
[SH] pip install defiance
<h2>documentation</h2>
[SH] defiance shares
<h2>defiance of defiance (the internal defiance of the defiance module)</h2>
<p>These checks are run with pypi "body_scan"</p>
<p>"defiance" is a fork of "body_scan"</p>
<p>("body_scan" checks are written with "unittest")</p>
[SH] defiance defiance
<h2>health checks</h2>
<p>Checks are started simultaneously, unless "--simultaneous no"</p>
<h3>create a status file</h3>
# status_1.py
def check_1 ():
print ("check 1")
def check_2 ():
print ("check 2")
def check_3 ():
raise Exception ("not 110%")
checks = {
"check 1": check_1,
"check 2": check_2,
"check 3": check_3
}
<h3>start from a directory deeper than the status file "status_1.py"</h3>
[SH] defiance status
<h3>The report then should appear like this:</h3>
<code>
paths: [
{
"path": "../status_1.py",
"empty": false,
"parsed": true,
"stats": {
"passes": 2,
"alarms": 1
},
"checks": [
{
"check": "check 1",
"passed": true,
"elapsed": [
4.054199962411076e-05,
"seconds"
]
},
{
"check": "check 2",
"passed": true,
"elapsed": [
1.72930003827787e-05,
"seconds"
]
},
{
"check": "check 3",
"passed": false,
"exception": "Exception('not 110%')",
"exception trace": [
"Traceback (most recent call last):",
" File \"/home/veganecology/.local/lib/python3.11/site-packages/defiance/processes/scan/process/keg/check.py\", line 68, in start",
" checks [ check ] ()",
" File \"<string>\", line 13, in check_3",
"Exception: not 110%"
]
}
]
}
]
alarms: [
{
"path": "../status_1.py",
"checks": [
{
"check": "check 3",
"passed": false,
"exception": "Exception('not 110%')",
"exception trace": [
"Traceback (most recent call last):",
" File \"/home/veganecology/.local/lib/python3.11/site-packages/defiance/processes/scan/process/keg/check.py\", line 68, in start",
" checks [ check ] ()",
" File \"<string>\", line 13, in check_3",
"Exception: not 110%"
]
}
]
}
]
stats: {
"alarms": 0,
"empty": 0,
"checks": {
"passes": 2,
"alarms": 1
}
}
</code>
<h2>advanced configurations</h2>
<p>
It's recommended to run defiance programmatilly.
An example of this can be found in the "advanced configurations"
section of the documentation.
</p>
<h2>Contacts</h2>
<p>status600@proton.me</p>
</pre>
Metadata
Release files for defiance 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| defiance-1.0.0.tar.gz | 72.9 kB | Without provenance | Details for defiance-1.0.0.tar.gz |
Release files / defiance-1.0.0.tar.gz
| Download URL | defiance-1.0.0.tar.gz |
|---|---|
| Size | 72.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4c5f122ca8a18367467383c2fdae5a6888e5d8ecfb1507c33acdae6274547a5
|
|
BLAKE2b-256 checksum How to use checksums |
3fc27dd4f1e3bc0c31d526ab442b46608d981a19caadb13e98229a9afa4c4a5f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for defiance 1.0.0
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.