C-Two Python SDK
C-Two exposes stateful Python resources through typed CRM contracts over same-process calls, local IPC, or an external HTTP relay. This package projects the shared Rust runtime into Python.
Python C-Two 0.8.2 pairs with c3 0.4.1. See the release and migration notes.
Install the matching published versions:
uv pip install 'c-two==0.8.2'
# Only for FastDB Payload contracts:
uv pip install 'c-two[fastdb]==0.8.2'
The base package has no Python runtime dependencies. Ordinary CRM definition,
registration, direct/IPC/relay calls and errors do not load FastDB or NumPy.
The fastdb extra pins fastdb4py==0.2.3; using FastDB payloads without it
reports the extra to install. The exact pin selects the validated 0.x binding
instead of allowing an untested later native interface.
Local IPC uses Unix domain sockets or current-logon-SID Windows Named Pipes. Unix roots select the final endpoint directory, with short names and directory-relative connections. Rust owns Persistent/OwnerBound policies, structured shutdown and scoped maintenance. Install matching builds across communicating clients, resource servers and c3. See the lifecycle guide.
cc.connect(..., timeout=...) bounds connection acquisition across pool waiting, handshake and route discovery. cc.with_call_options(proxy, timeout=...) sets business-call waiting separately. Custom Unix endpoint directories can use 0755 when the current user owns them and other identities cannot modify them; Windows uses its SID-scoped pipe namespace. See connection deadlines and endpoint configuration.
cc.set_server(startup_timeout=30.0) sets the native startup wait before registration. Omitted/None retains the finite five-second default; zero expires immediately. Startup expiry is identified by CoreError.lifecycle_kind == 'startup_timeout', with startup_stage and timeout_seconds; bind I/O failures keep their OS fields without a configuration-error label. See server startup deadlines for freezing and cleanup semantics.
IPC uses lazy buddy pools, idle decay and finite backing/reassembly budgets; pool_enabled=False skips buddy. cc.memory_stats() observes native accounting; held responses and borrowed inputs retain independent leases. The standalone relay has its own upstream policy. See the memory guide.
Use cc.connection_events() for one cancellable, bounded stream of incoming and outgoing physical IPC events, tagged by side. ConnectionObservation.snapshot() retains late inspection; its old blocking wait_closed() is removed. Physical observations work without a pending call. OwnerBound hosts support explicit, single-use recovery tickets during the original grace period. Bind/connect failures preserve io_kind, raw_os_error and io_operation on public cc.error.CoreError. These features share the Rust implementation on macOS, Linux and Windows x64 and ARM64; see the lifecycle guide for API examples.
Development
Use canonical main for source development and run commands from the repository root. Python patch-release provenance is recorded with its release notes; the c3 release's rc-manifest.json identifies that CLI release's source, which can differ from a later Python patch:
git clone https://github.com/world-in-progress/c-two.git
cd c-two
Prerequisites:
- Python 3.10 or newer
- Python 3.12 for standard local development
- Python 3.14.3t when testing free-threading support
- Rust toolchain
uv- for full interoperability tests: the FastDB
v0.2.3source checkout at../fastdb
The default workspace dev group selects c-two[fastdb] and resolves
fastdb4py==0.2.3 from PyPI. Bare package installation omits it. The Python native extension and
c3 pin FastDB source abba785ef2a7d3fbee1bbc608393a3e6c7b042c4 for their source-mode static
builds. Core and Rust SDK tests use the published Rust bindings with the matching
FastDB Core SDK
in system link mode. Golden specs and TypeScript interoperability fixtures still
need the sibling source checkout; it is not a Python package override.
Install dependencies and build the Python native extension. This also compiles the required Rust core crates; no separate Rust prebuild step is needed:
FASTDB_PAYLOAD_LINK_MODE=source uv sync
Rebuild the native extension after changing Rust code:
FASTDB_PAYLOAD_LINK_MODE=source uv sync --reinstall-package c-two
Relay-dependent tests and examples require the standalone c3 binary. From a
source checkout, build and link it before running relay flows:
FASTDB_PAYLOAD_LINK_MODE=source python tools/dev/c3_tool.py --build --link
The Python SDK does not embed or start a relay server. Start the standalone
Rust relay with c3 relay, Docker Compose, or orchestration such as
Kubernetes, then point Python code at its relay anchor with
C2_RELAY_ANCHOR_ADDRESS or cc.set_relay_anchor(). The anchor is used for
registration and name resolution. Remote HTTP calls still use the resolved
route's relay_url directly, and local direct IPC is selected only for a
loopback/local anchor.
Relay-aware clients preflight routes before the first call and re-resolve
structured stale-route responses; set C2_RELAY_ROUTE_MAX_ATTEMPTS to tune the
maximum route acquisition attempts (default 3, valid range 1..=32, 0 is
treated as 1). Ambiguous data-plane failures are not replayed.
After the source-mode build, configure the absolute Core SDK library directory for Rust consumers spawned by interoperability tests. Follow the development setup in the repository README and Windows guide for platform-specific loader paths and test prerequisites. Keep the existing extension build while running the Python tests:
C2_RELAY_ANCHOR_ADDRESS= uv run --no-sync pytest sdk/python/tests -q -n 4 --timeout=30
The four-worker command is for Linux/macOS; omit -n 4 on Windows. See the test guide for prerequisites and longer real-idle and interoperability cases.
Run Rust core checks when validating shared native runtime changes:
cargo test --manifest-path core/Cargo.toml --workspace
For CLI build, link, and test commands, see the CLI guide.
Examples
Python examples live under ../../examples/python/:
uv sync --group examples
uv run python examples/python/local.py
Relay examples also need a running standalone relay, for example:
FASTDB_PAYLOAD_LINK_MODE=source python tools/dev/c3_tool.py --build --link
c3 relay --bind 127.0.0.1:8080
Benchmarks
Python-specific benchmarks live in benchmarks/:
C2_RELAY_ANCHOR_ADDRESS= uv run python sdk/python/benchmarks/segment_size_benchmark.py
1 maintainer
Metadata
1 maintainer
Release files for c-two 0.8.2
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 | |
|---|---|---|---|---|
| c_two-0.8.2.tar.gz | 1.2 MB | With provenance | Details |
Built distributions (wheels)
Total release size: 167.6 MB
Release files / c_two-0.8.2.tar.gz
| Download URL | c_two-0.8.2.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5937af9cac2fbbce34310d3f088c94fe341bf7a5607d530806127f1dece1fded
|
|
BLAKE2b-256 checksum How to use checksums |
dd89536ff4d08b1df66343f3dc03ff9fa24521c462775604fb0ae055f3c783f1
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314t-win_arm64.whl
| Download URL | c_two-0.8.2-cp314-cp314t-win_arm64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows ARM64 |
|
SHA-256 checksum How to use checksums |
47e08a3692762f29f33df3ed09d6521347a1347c74ee02fef79b9892bc160517
|
|
BLAKE2b-256 checksum How to use checksums |
f7ccf413247a74f0acd7203593af80bd1b4748ed8c648bdd0562573fcfc3a444
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314t-win_amd64.whl
| Download URL | c_two-0.8.2-cp314-cp314t-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9c4b5c7d74807aabb34b3ae01718deb0141c78c91f29d569f71c92bc8ce8b5a8
|
|
BLAKE2b-256 checksum How to use checksums |
c5d85ddd7d4664c728d8ccdd2439368b8ca287b0b0ce5cb060d478b8ba235780
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | c_two-0.8.2-cp314-cp314t-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
ddcd7b8a1f10873ec4f317174b99c8dccf238b83783586c021e7a96c1a5e945c
|
|
BLAKE2b-256 checksum How to use checksums |
11370eb076e02d060ff6797e6eb25be92e8392f225ed1e5906f6d0adf9c18d4e
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | c_two-0.8.2-cp314-cp314t-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
a101c8ddeaa10a8f62f10516c6685288f212f89d68b35e877c9e1ebaf2993d01
|
|
BLAKE2b-256 checksum How to use checksums |
bd8cb8c07fabe51e6d3e47d6a174b631f28f8f898533a03502ff45725867435a
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314t-macosx_11_0_arm64.whl
| Download URL | c_two-0.8.2-cp314-cp314t-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1efbc7177d33d39f7fadeff9651c2465b105276371f8536335906504b08ad0e0
|
|
BLAKE2b-256 checksum How to use checksums |
112bcca7591b074b530cde43a66cc2a5bc32f596ac9cf129f1c0b735add1a59a
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314t-macosx_10_12_x86_64.whl
| Download URL | c_two-0.8.2-cp314-cp314t-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.14 CPython 3.14 free-threading macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
669f37b8570e45c90819d8a036c544f1511eaa04b9f659b55223753eb79f9601
|
|
BLAKE2b-256 checksum How to use checksums |
af1750abe727302064b57a66421b16b515c2be8ae3338a714259cdd09594ee39
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314-win_arm64.whl
| Download URL | c_two-0.8.2-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
9aaff72d9173b8701b7d3f688a01768800fbd06a52ff6c21e06fab33b6519e66
|
|
BLAKE2b-256 checksum How to use checksums |
3352e4fcdb207c8bd9f9b619b54441a311c41af211bacdec531efbdb4580247a
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314-win_amd64.whl
| Download URL | c_two-0.8.2-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
ec2e01b4897309c8b075303ad06edffa8df9729aa126683eac0db7952761fd05
|
|
BLAKE2b-256 checksum How to use checksums |
9063b4a2c994515be4183ec0710297420102dffac880593f36a5f7deaf2d073d
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | c_two-0.8.2-cp314-cp314-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
20e811931c983d254a9ec7bbc09d146a3d1b87aeefa84e139fcd55699df32742
|
|
BLAKE2b-256 checksum How to use checksums |
978aa2fa71eb22d403356a4f7bf1364df0ccf3f418035e757633da19450af2e5
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | c_two-0.8.2-cp314-cp314-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.14 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
6c7feefcaf988027f85e26596c312f68e106ba4d771fed9c901a3a7aa5f366b9
|
|
BLAKE2b-256 checksum How to use checksums |
0df022dfc7c72bb5dd50c5a64d91898b0ef3acbdc4130a5a10450dd2b2ee8159
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | c_two-0.8.2-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
4742a40f444112826be4213d3acd3cd228025e68174630a3c12a24d4579fed30
|
|
BLAKE2b-256 checksum How to use checksums |
4717bc5a02e778a9b27398a8eccc7c7953431d6e52e703a4e5a5c255cdf155dd
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp314-cp314-macosx_10_12_x86_64.whl
| Download URL | c_two-0.8.2-cp314-cp314-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.14 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
9e1816de36c496547f1f5fac719c25bf8a08916b0609cbc8cbdfdccd2bb5d24a
|
|
BLAKE2b-256 checksum How to use checksums |
e16e4173fae4431fc82b962fc6df022e8b064a739366b3d86f195a8a63cedfbc
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp313-cp313-win_arm64.whl
| Download URL | c_two-0.8.2-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
ce337d3043fc0fcebbe9dee46bc09e37f341018258dfec3d651723d8de1d1657
|
|
BLAKE2b-256 checksum How to use checksums |
c2407130ee25abf84242e334f3546abf4bb80ae2dfe80c2bcc58c44ea9c51e2d
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp313-cp313-win_amd64.whl
| Download URL | c_two-0.8.2-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c969688a8b8af3b6a78de75dc84e78397f1a763e9521a8b95d9cfaf6bc6af0cb
|
|
BLAKE2b-256 checksum How to use checksums |
705b3a35f5ede4fea4b684fbf58337036435c33163dc2ac6434d289c7d733000
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | c_two-0.8.2-cp313-cp313-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
e8b50dd14fb6b9a2e9b4347d8eb51faa8a81505d15a1a531af1fb319fcdf224a
|
|
BLAKE2b-256 checksum How to use checksums |
cc8a44e5211bf1d2c643720e8368849544ec59aab29397b0f9007111c01913a5
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | c_two-0.8.2-cp313-cp313-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
8e9a55bea4fc782809d5d02200c9cdf91cb33aa07570ce105d6e1adfefb564c4
|
|
BLAKE2b-256 checksum How to use checksums |
5a8753a9a7dd8fd7d0c18a3b2bba6be765f4845ded9b1d56560bc4cabe2d24f9
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | c_two-0.8.2-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
7448182381fb2912bf4e86c32bd9095d5efedf54c7bceebc9cb0d0f6f6d857fe
|
|
BLAKE2b-256 checksum How to use checksums |
e669653aca0f4d5948e52d34ed35f05ee335e5f71a21b67d522580eb52ddb244
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp313-cp313-macosx_10_12_x86_64.whl
| Download URL | c_two-0.8.2-cp313-cp313-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.13 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
21737fc7469de398fb72258a7da6dab0663c1be265fa3ed273dea769e190a2a5
|
|
BLAKE2b-256 checksum How to use checksums |
be27c824780f22750cc5226e598e4dec8753dd390d229339ccbe27ef06b6955b
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp312-cp312-win_arm64.whl
| Download URL | c_two-0.8.2-cp312-cp312-win_arm64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.12 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
c1a25e75b4d1a4fa81c6ccddbfb6ccbf15f42127e5953945aa99a8f2bfa41d6b
|
|
BLAKE2b-256 checksum How to use checksums |
eace1718d07b73af15024b1f7bb14d88c4e58e7df8dd269cf4711537651fcb89
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp312-cp312-win_amd64.whl
| Download URL | c_two-0.8.2-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
b7dfa777b02e9f4cf73ea1ecf329d98e0a1127cc4e7ade91719fb4bf0325db08
|
|
BLAKE2b-256 checksum How to use checksums |
ce7bd6000bb9a37294d929fd03486065ee389e82545a74b2dff23eaa64b367d7
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | c_two-0.8.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
86da68893b2a1dbd969168047b643fbdf06f548d56dd4a68cd463ebed77f34d8
|
|
BLAKE2b-256 checksum How to use checksums |
fb69ee74ae2356ea50c0b6b33ccba5ad839550bbbf805569ea5b894adfb85131
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | c_two-0.8.2-cp312-cp312-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
5b7a598fccee3ad3ef045de8b1ea22db894a97dd86da5ffe906f1afbf4d89246
|
|
BLAKE2b-256 checksum How to use checksums |
e0b66d13139868ec43a48a3ddd35643e1de21b9b4a4f246d5c74eb44d1c2e34d
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | c_two-0.8.2-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
0bcf50003acd843effb30b72e25456a211b01c5e2b8cdce0a01d3c4fa4762f4d
|
|
BLAKE2b-256 checksum How to use checksums |
b99b8b5fdf08f475bdb5af769bfaba8091b6ecc1366dd3260eeb8d50cee8d898
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp312-cp312-macosx_10_12_x86_64.whl
| Download URL | c_two-0.8.2-cp312-cp312-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.12 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
2eda4aa4d8b97ab713a67ebe77078cf459e37574d46f9e661fc9c30a10700b7a
|
|
BLAKE2b-256 checksum How to use checksums |
8dcef11cd0d5c61ff6af4d548b55cfcdab7f0603ddb8ccde574f3c9858334c24
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp311-cp311-win_arm64.whl
| Download URL | c_two-0.8.2-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 4.3 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
b5a8f82d726079a92896b7a148e7f5fb252e4103da30a88bd1ffe28f9d980597
|
|
BLAKE2b-256 checksum How to use checksums |
726aa5fc4228fa0f3b896ceb018a2f41438a598e81ee279f873ac0b709f00e58
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp311-cp311-win_amd64.whl
| Download URL | c_two-0.8.2-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
7d08d13427e58fd458ee929d4888f8f8212405c3b009919eb477c37356516f79
|
|
BLAKE2b-256 checksum How to use checksums |
78eaa73d3fa0da5203729125a9408ab0e7e3eb98a2e8201a3794d8223e038fe3
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | c_two-0.8.2-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
764dc7ab4111880393a859bcd671fafc08a6b1f3fa0a6b755043847b67186d6c
|
|
BLAKE2b-256 checksum How to use checksums |
250b6419c17b2457a998795459ac6e8afb6c74471e25b71ab04f6bc32743f672
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | c_two-0.8.2-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
f5857ef7c804d6c4c34edb02df4821d6fd83d1386f836618ccff3fadac9331e8
|
|
BLAKE2b-256 checksum How to use checksums |
5e120ca89f130c301b27a9d2517592a714fc6cf36b782cb1a7ab4d0f39142409
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | c_two-0.8.2-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
dbef08a5429f370563dfbd77c723fabd665a50a5889e50c55f4d168ee784e51b
|
|
BLAKE2b-256 checksum How to use checksums |
e66a16619ff449d8bba6b2f3ca4822c8d54cd79cc69cee972d26322c8ca6edea
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp311-cp311-macosx_10_12_x86_64.whl
| Download URL | c_two-0.8.2-cp311-cp311-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.11 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
8a0c817a838791c49c541fe1f5cc99688fd3a3b8fd82d89e8329257932f652c2
|
|
BLAKE2b-256 checksum How to use checksums |
03a9bc1745ec5a66bf2b099933fea5c6169d5b3d11ace753c008768489789bdf
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp310-cp310-win_amd64.whl
| Download URL | c_two-0.8.2-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
90000639d6394f705528c6db7ecced57b4d901ac2907c43327ada66a8c9b58cb
|
|
BLAKE2b-256 checksum How to use checksums |
d58434e9aa6d29fe25a3b37302ae1046f5c1748764d90d124c6c287e8a88695d
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | c_two-0.8.2-cp310-cp310-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 5.4 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 |
|
SHA-256 checksum How to use checksums |
28a42f5cd6c676456c1167af9933af0ddf3974e0164bc48b62dc8bddba0a5b9a
|
|
BLAKE2b-256 checksum How to use checksums |
63fcf11418e93ca9c04c452ad5da3a889b14468283250c3160f0a58707ae69ce
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | c_two-0.8.2-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 5.5 MB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 |
|
SHA-256 checksum How to use checksums |
7634a098e54490e35c40704fb266f685f3daeb3764dcdac6594c2863e27435c0
|
|
BLAKE2b-256 checksum How to use checksums |
89e4b4cfdde564e2509c7a441f54416f35aa0979241846f70b1c4280544e222d
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | c_two-0.8.2-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 4.4 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d4f4a6f9a1bf945c2d4445d54a047f49b53674850469207afd687bd8fd74e52e
|
|
BLAKE2b-256 checksum How to use checksums |
6e9eb93e3a53e4d0d89d694f019c10e23b897b36391edec71329f340363a45cb
|
| 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 23, 2026.
Transparency logRelease files / c_two-0.8.2-cp310-cp310-macosx_10_12_x86_64.whl
| Download URL | c_two-0.8.2-cp310-cp310-macosx_10_12_x86_64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.10 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
95ec9274a61a1eff6cce16709f0e6fa2e53f57ec4c2ec28b9f4052fd04b59ff3
|
|
BLAKE2b-256 checksum How to use checksums |
2d9e3222795f57ec96eb9282b211aa103ea84c46ab2df155f04c26720d88901a
|
| 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 23, 2026.
Transparency logSecurity for c-two 0.8.2
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 36 files in this release have been uploaded with provenance metadata.
Attestation for c_two-0.8.2.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 23, 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.
