Quick Start
Ecosystem Plugin for Kava support in Ape
Dependencies
- python3 version 3.8 up to 3.11.
Installation
via ape
You can install this plugin using ape:
ape plugins install kava
or via config file:
# ape-config.yaml
plugins:
- name: kava
via pip
You can install the latest release via pip:
pip install ape-kava
via setuptools
You can clone the repository and use setuptools for the most up-to-date version:
git clone https://github.com/ApeWorX/ape-kava.git
cd ape-kava
python3 setup.py install
Quick Usage
Installing this plugin adds support for the Kava ecosystem:
ape console --network kava:mainnet
Development
This project is in development and should be considered a beta. Things might not be in their final state and breaking changes may occur. Comments, questions, criticisms and pull requests are welcomed.
1 maintainer
Metadata
1 maintainer
Release files for ape-kava 1.0.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 | |
|---|---|---|---|---|
| ape-kava-1.0.1.tar.gz | 15.2 kB | Without provenance | Details |
Release files / ape-kava-1.0.1.tar.gz
| Download URL | ape-kava-1.0.1.tar.gz |
|---|---|
| Size | 15.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dcc900148a7132aed51a389bec7e67f8af394cbbd873ded73e4a14ab2c424294
|
|
BLAKE2b-256 checksum How to use checksums |
fdeb0031669e5ad0c5de7ac3612020705e822c7f250f5be466aa9ac7d7899c48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for ape-kava 1.0.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.
