The Python client library for the CEPT API. See https://cept.3scale.net for additional resources.
Installation
pycept includes a setuptools-compatible setup.py for your convenience. Dependencies are listed in setup.py and will be installed automatically as part of any of the techniques listed below. Otherwise, you will need to install the following external dependencies before using grokpy:
1 maintainer
Metadata
1 maintainer
Release files for pycept 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 | |
|---|---|---|---|---|
| pycept-1.0.0.tar.gz | 4.4 kB | Without provenance | Details |
Release files / pycept-1.0.0.tar.gz
| Download URL | pycept-1.0.0.tar.gz |
|---|---|
| Size | 4.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa17678d9d09794af2c16ec43f40547a0e5b61272cd5cb720595943a8d636c51
|
|
BLAKE2b-256 checksum How to use checksums |
ce9c1dd81b17838987c38ad913132ef56087931caeeb5559ae3dd5cafc0c941d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pycept 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.
