kraken-std
The Kraken standard library.
Development
Integration testing
Integration tests are located in src/tests/integration. The following tools need to be available to run the
integration tests:
- Cargo (to test Cargo building and publishing) The Cargo integration tests run against Artifactory and Cloudsmith and requires credentials to temporarily create a new Cargo repository (available in CI).
- Docker (used to setup services that we run integration tests against)
- Helm (to test Helm packaging and publishing)
- Poetry (to test Python publishing and installing)
- Slap (to test Python publishing and installing)
Test a single integration test
PYTEST_FLAGS="--log-cli-level DEBUG -s -k <test_filter>" kraken run pytestIntegration -v
The integration tests create temporary files that need to be mounted into a Docker container. If you are running
the integration tests in a Coder workspace, you may need to set TMPDIR=$HOME/tmp as the workspaces often only
share the home volume with the Docker-in-Docker container.
Pull Requests
By default, Pull Requests require a changelog entry to be added via the slap changelog add command. If no changelog
entry was added, CI will fail. Some changes are not relevant to consumers of the API that they do not need to be
recorded in the changelog, such as typos in the README. In such cases, the no changelog label can be added to the
Pull Request.
2 maintainers
Metadata
2 maintainers
Release files for kraken-std 0.31.7
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 |
|---|---|---|---|---|
| kraken_std-0.31.7.tar.gz | 84.7 kB | Without provenance | Details for kraken_std-0.31.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kraken_std-0.31.7-py3-none-any.whl | Python 3 | none | any | Details for kraken_std-0.31.7-py3-none-any.whl |
Total release size: 209.9 kB
Release files / kraken_std-0.31.7.tar.gz
| Download URL | kraken_std-0.31.7.tar.gz |
|---|---|
| Size | 84.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d66510a9c762227e0a7fd5df4b7d2292ca865ea723a1b4598c5239bf65046378
|
|
BLAKE2b-256 checksum How to use checksums |
a692adf15cfa3fabdc9dd93cd234f2d2b67220a8306dc24ebadaf61def4017a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.9.6 readme-renderer/37.3 requests/2.30.0 requests-toolbelt/1.0.0 urllib3/2.0.2 tqdm/4.65.0 importlib-metadata/6.6.0 keyring/23.13.1 rfc3986/2.0.0 colorama/0.4.6 CPython/3.10.2
|
Release files / kraken_std-0.31.7-py3-none-any.whl
| Download URL | kraken_std-0.31.7-py3-none-any.whl |
|---|---|
| Size | 125.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eb2c85ee861d39695f7a6dbdd3d2de3094d0f492d635cb7a8237c6e38bb73dd2
|
|
BLAKE2b-256 checksum How to use checksums |
2cba6056ee3c68d70facfec45670e3c22f1a2ba8d62797d57c4549949cd3433a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 pkginfo/1.9.6 readme-renderer/37.3 requests/2.30.0 requests-toolbelt/1.0.0 urllib3/2.0.2 tqdm/4.65.0 importlib-metadata/6.6.0 keyring/23.13.1 rfc3986/2.0.0 colorama/0.4.6 CPython/3.10.2
|
Security for kraken-std 0.31.7
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.
