sushicore
The shared core of the Sushi developer CLIs. hub, sr, se, sa, sb, sd and st all
import it for the same five things: locating a workspace, loading layered TOML configuration,
printing to a terminal or to a JSON stream, driving cmake and ctest, and reading the
sushistack.deps.toml fragment a repository writes about what it needs.
pip install sushicore
It is a library for those CLIs rather than a tool of its own: it installs no console script and it knows nothing about SYCL, a renderer, or any one module's schema.
| Module | What it does |
|---|---|
sushicore.workspace |
Walks up for a marker, merges a [tool] table with its platform override |
sushicore.config_base |
The layered load: defaults, file, local file, environment |
sushicore.console, renderer, events, theme, icons |
One seam for human output and for --json |
sushicore.cmake_driver, cmake_cache, proc, toolchain_args |
The configure, build and test driver the CLIs share |
The manual is in docs/README.md. Licensed under the terms in LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for sushicore 0.3.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 | |
|---|---|---|---|---|
| sushicore-0.3.0.tar.gz | 54.2 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sushicore-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.2 kB
Release files / sushicore-0.3.0.tar.gz
| Download URL | sushicore-0.3.0.tar.gz |
|---|---|
| Size | 54.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
362d8e0292c4c5ae9ee0d4d89b147346004d0d3eddac6e92612a6d53307c64ac
|
|
BLAKE2b-256 checksum How to use checksums |
74ad1f7241b47d27ba4b1b41c68147f1d7f2c9fa1d29e35b2f7bccead2979c55
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logRelease files / sushicore-0.3.0-py3-none-any.whl
| Download URL | sushicore-0.3.0-py3-none-any.whl |
|---|---|
| Size | 50.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cff07e9a2915a6cee881ffc7f17651569696cb3830bea47760be6f08a4c292a3
|
|
BLAKE2b-256 checksum How to use checksums |
316a2277ae3a16656be6b97924d4cc8615544948c70716659e89d8bd45e47473
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logSecurity for sushicore 0.3.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for sushicore-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logA 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.
