graphcore-distro (distro backend)
Consumer-facing pip package graphcore-distro: the graphcore CLI, project
scaffolding, and the kernel and built-in apps at versions released together. The wheel is a bundle of sibling
import packages. graphcore_cli is only the command surface (argparse +
dispatch). Anything a caller might import without going through the
graphcore command is its own package; the CLI consumes it, the same way it
consumes graphcore_user_guides. Generic components never live inside
graphcore_cli/.
distro/backend/
graphcore_cli/ # command surface only
graphcore_project/ # operate a generated project — import graphcore_project
graphcore_user_guides/ # curated markdown
graphcore_project_kit/ # scaffold, skills, infra, scripts (assets only)
doc_topics.py # guide topic registry
graphcore_project is the library for a generated project on disk: find the
root, read .env, migrate, run. The CLI consumes it; callers that want the
same operations without the CLI import this package. It is not
graphcore_project_kit — that package is assets, not Python. The on-disk
unit is a project; "deployment" in the vision docs means a running
backend, not this directory.
Requires Python 3.13+; generated projects run 3.14.
pip install graphcore-distro
graphcore startproject myproj
To develop the framework, install the monorepo's packages as editables
instead (pip install -r requirements-dev.txt from the monorepo root) and
generate projects with graphcore startproject --local-framework. Redis is included for
multi-process deploys; you can still point settings.py at LocMem or another
cache if you do not want to use it.
Tests
From the monorepo root, with the shared Postgres running (graphcore infra up):
scripts/test # every suite on Postgres, database-dependent suites on SQLite
scripts/test graphcore_cli # narrow to a test label, on every database
See .agents/skills/run-tests/SKILL.md for the options.
CLI surface
graphcore startproject, startapp, apps list, run, migrate, test,
dev reset, docker, infra, db, api, docs, frontend, skills.
graphcore apps list prints every discovered app and its provenance
(entry point: <dist> or apps/ directory).
Metadata
Release files for graphcore-distro 0.1.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 | |
|---|---|---|---|---|
| graphcore_distro-0.1.0.tar.gz | 184.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| graphcore_distro-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 409.2 kB
Release files / graphcore_distro-0.1.0.tar.gz
| Download URL | graphcore_distro-0.1.0.tar.gz |
|---|---|
| Size | 184.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbee14734fb5ac16d5ca0118049c46711576f8c65b393d99b586f334567ac2bc
|
|
BLAKE2b-256 checksum How to use checksums |
43a1ceb4b7efd6e4a5764052c0dde351ab96ce4b68b709da0fdf7d9884c1e112
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 20, 2026.
Transparency logRelease files / graphcore_distro-0.1.0-py3-none-any.whl
| Download URL | graphcore_distro-0.1.0-py3-none-any.whl |
|---|---|
| Size | 224.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa2b28ca33c5e002f0b0e7c05556367f4565328fc248a31a6b5bd64296574cd4
|
|
BLAKE2b-256 checksum How to use checksums |
75cfac5f41d7623e5ba4d58322c6b0f787167be09c4ddacf2f6526e253597699
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 20, 2026.
Transparency logSecurity for graphcore-distro 0.1.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 graphcore_distro-0.1.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 Oct 20, 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.