datacoco-sf_tools
Installation
datacoco-sf_tools requires Python 3.6+
python3 -m venv <virtual env name> source <virtual env name>/bin/activate pip install datacoco-sf-tools
Quickstart
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_sf_tools are welcome!
Please reference guidelines to help with setting up your development environment here.
1 maintainer
Metadata
1 maintainer
Release files for datacoco-sf-tools 0.1.1
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-sf_tools-0.1.1.tar.gz | 6.5 kB | Without provenance | Details |
Release files / datacoco-sf_tools-0.1.1.tar.gz
| Download URL | datacoco-sf_tools-0.1.1.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6705628f6ea7dd718e72c6c9ab71975011ed23749e5551452fe0d51ebe2e1983
|
|
BLAKE2b-256 checksum How to use checksums |
a9ce85dcda01c993aa551b9294a56dc69d37a5e3a00622b57b153bd8fe95247c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.6.5
|
Security for datacoco-sf-tools 0.1.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.
