Skip to main content

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.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for graphcore-distro 0.2.0
File Size Uploaded Provenance
graphcore_distro-0.2.0.tar.gz 188.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for graphcore-distro 0.2.0
File Interpreter ABI Platform
graphcore_distro-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 417.8 kB

Release files / graphcore_distro-0.2.0.tar.gz

Download URL graphcore_distro-0.2.0.tar.gz
Size 188.4 kB
Tags Source
SHA-256 checksum
How to use checksums
63920747239f1270012eadf888ed5d320fbe45ba2ed5ef99995d2b40b3a37aaf
BLAKE2b-256 checksum
How to use checksums
f40a2c974361f722cb479906ff436fcc52639da52cb50618fa02b7c8e5f00ad3
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 22, 2026.

Transparency log

Release files / graphcore_distro-0.2.0-py3-none-any.whl

Download URL graphcore_distro-0.2.0-py3-none-any.whl
Size 229.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
6fa8cbcc842304e86191dd027afa2db0e6ce57b595f503db38d3b2f8dba535c2
BLAKE2b-256 checksum
How to use checksums
712c53c0cdbfa494719ad2e464e5e75b19d4badd3cc7f2253d24023204998385
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 22, 2026.

Transparency log

Security for graphcore-distro 0.2.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.

Select from 2 files

Attestation for graphcore_distro-0.2.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 22, 2026.

Transparency log

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.

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page