Batch is a simple interface for managing the state of jobs and workflows in batchy microservice.
Installation
datacoco-batch requires Python 3.6+
python3 -m venv <virtual env name> source <virtual env name>/bin/activate pip install datacoco-batch
Quickstart
self.batchy = Batch(
wf=test_workflow,
server="server.com",
port="80",
)
self.batchy.open()
self.batchy.get_status()
self.batchy.close()
Sample output
{
"global": {
"batch_id": "123456789",
"status": "success",
"failure_cnt": 0,
"open_cnt": 2,
"batch_start": "2020-01-17T06:58:01.234567",
"batch_end": "2020-01-17T07:18:08.012345"
}
}
Development
Getting Started
It is recommended to use the steps below to set up a virtual environment for development:
python3 -m venv <virtual env name> source <virtual env name>/bin/activate pip install -r requirements.txt
Testing
pip install -r requirements-dev.txt
To run the testing suite, simply run the command: tox or python -m unittest discover tests
Contributing
Contributions to datacoco_batch are welcome!
Please reference guidelines to help with setting up your development environment here.
Metadata
Release files for datacoco-batch 0.1.2
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 | |
|---|---|---|---|---|
| datacoco-batch-0.1.2.tar.gz | 2.9 kB | Without provenance | Details |
Release files / datacoco-batch-0.1.2.tar.gz
| Download URL | datacoco-batch-0.1.2.tar.gz |
|---|---|
| Size | 2.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cea69914c16b9c8481f8d4bf43ad2a5db5ce45087af42a13c46dcdbe6849c7ec
|
|
BLAKE2b-256 checksum How to use checksums |
8c320af7e2787320530bb6c4d640c59f277483e65539f2c1f661251608e84782
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.22.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.4
|
Security for datacoco-batch 0.1.2
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.