chalk-remote-call-python
A Python runtime interface for Chalk's RemoteCallService. This package provides a gRPC server backed by a Rust implementation (tonic + PyO3) that lets you define a handler(event, context) function to process incoming Arrow-serialized requests.
The server receives Arrow IPC record batches over a bidirectional gRPC stream, transforms them into a Python dict, invokes your handler, and streams the results back as Arrow IPC.
Requirements
- Python >= 3.10
- Rust 1.99.0 (for building the native extension)
pyarrow >= 14.0.0
Usage
1. Write a handler
Create a Python module with a handler function:
# my_handler.py
import pyarrow as pa
import pyarrow.compute as pc
def on_startup():
"""Optional -- runs once before the server starts accepting requests."""
print("Loading model weights...")
def handler(event: dict[str, pa.Array], context: dict) -> pa.Array:
"""Called for each incoming request.
Args:
event: dict mapping column names to pyarrow.Array values.
context: dict with request metadata
Returns:
A pyarrow.Array, pyarrow.RecordBatch, pyarrow.Table, list, dict, or scalar.
The framework auto-converts the result to Arrow IPC for the response.
"""
return pc.multiply(event["x"], event["y"])
def on_shutdown():
"""Optional -- runs once after the server stops accepting requests."""
print("Releasing resources...")
2. Start the server
chalk-remote-call --handler my_handler.handler
Or via python -m:
python -m chalk_remote_call --handler my_handler.handler
CLI options
| Flag | Env var | Default | Description |
|---|---|---|---|
--handler |
(required) | Dotted path to handler function | |
--port |
CHALK_REMOTE_CALL_PORT |
6666 |
Port to listen on |
--host |
CHALK_REMOTE_CALL_HOST |
[::] |
Host to bind to |
--workers |
CHALK_REMOTE_CALL_WORKERS |
10 |
Tokio runtime worker threads |
--on-startup |
Dotted path to a startup function | ||
--on-shutdown |
Dotted path to a shutdown function | ||
--log-level |
INFO |
DEBUG, INFO, WARNING, or ERROR |
The CLI writes Python logs to stderr as one JSON object per line, with separate
timestamp, severity, logger, and message fields. Exceptions include an
exception.stacktrace field, which the log collector uses for the traceback.
CLI logging is configured before importing runtime dependencies. Import failures,
invalid environment configuration, and exceptions escaping startup or the server
emit a single ERROR record with the full traceback and exit with status 1.
Calls to serve() from Python retain the embedding application's logging configuration.
On Linux, server shutdown drains buffered function-call metrics before the runtime exits,
including when the server returns an error. Draining waits up to 10 seconds; a timeout or
publisher failure is logged as a warning.
Routine drain messages are logged at DEBUG; set RUST_LOG=info,_native::metrics=debug
to include them.
Missing optional StatsD endpoints or a metrics-bus topic do not emit warnings.
Failures initializing configured metrics sinks still warn. Routine customer
StatsD configuration messages are emitted at DEBUG by the shared metrics library;
set RUST_LOG=info,chalk_metrics::metrics::config=debug to include them.
Environment variables
| Variable | Description |
|---|---|
CHALK_INPUT_ARGS |
Comma-separated list of column names (e.g. x,y,z). Renames incoming RecordBatch columns by index. If unset, the original column names are used. Reserved columns (below) are held out of this mapping and keep their own name. |
CHALK_FNQ_CONSUMER_ENDPOINT |
Opt into DP API FnqConsumerService consumption (HTTP or HTTPS gRPC endpoint). Unset preserves direct Redis consumption. API errors never fall back to Redis. |
CHALK_FUNCTION_QUEUE_TOKEN_FILE |
Controller-mounted working JWT, reopened per RPC to observe rotation. Defaults to /var/run/secrets/chalk-function-queue/identity-token. The shim does not exchange credentials. |
CHALK_FNQ_QUEUE_PROTOCOL |
Self-consumer work transport: list_v1 (default/backward compatible) or stream_v1. Deployment tooling sets this from immutable scaling-group revision metadata. |
Reserved columns
A caller may attach framework side-channel data to a request as an extra column. Reserved
columns are matched by name, are optional on any given request, and are excluded from the
positional CHALK_INPUT_ARGS mapping — so CHALK_INPUT_ARGS always lists exactly the
handler's declared arguments, whether or not the caller sent one.
| Column | Meaning |
|---|---|
__chalk_row_metadata__ |
Per-row binary blob supplied by the caller (Chalk's engine sets it from catalog_call(..., row_metadata => ...)). Handlers read it via chalkcompute.get_row_metadata(). |
3. Docker image
FROM python:3.11-slim
WORKDIR /app
RUN pip install chalk-remote-call-python
# Copy your handler code
COPY my_handler.py /app
EXPOSE 6666
ENTRYPOINT ["chalk-remote-call"]
CMD ["--handler", "handler.handler"]
Build and run:
docker build -t my-chalk-handler .
docker run -p 6666:6666 -e CHALK_INPUT_ARGS="x,y" my-chalk-handler
Programmatic usage
You can also start the server from Python:
from chalk_remote_call import serve
def handler(event, context):
return list(event.values())[0]
serve(handler=handler, port=8080)
Local Testing
Use grpcurl to verify the server is running:
# Check health
grpcurl -plaintext localhost:6666 grpc.health.v1.Health/Check
# List services via reflection
grpcurl -plaintext localhost:6666 list
Architecture
The server uses a Rust backend via PyO3:
- tonic — gRPC server with health checking and reflection
- prost — protobuf message handling
- arrow-rs — Arrow IPC validation
- PyO3 — FFI bridge to call Python handler functions
The Rust server runs on a tokio async runtime. When a request arrives, Arrow IPC bytes are passed to Python via PyO3 (spawn_blocking + GIL acquisition), where the handler is invoked. Results are passed back as IPC bytes.
Development
Setup
cd chalk-remote-call-python
uv venv --python 3.11
uv pip install -e ".[dev]"
Running tests
pytest tests/ -v
The Linux metrics shutdown regression tests use an in-memory bus publisher:
PYO3_PYTHON=python3 cargo test --manifest-path chalk-remote-call-rs/chalk-remote-call-server/Cargo.toml --no-default-features --lib metrics::tests
--no-default-features links Python into the test executable; wheel builds retain
the default extension-module feature.
Rust code
Rust source lives in chalk-remote-call-rs/:
To check the Rust code independently:
PYO3_PYTHON=python3 cargo check --manifest-path chalk-remote-call-rs/chalk-remote-call-server/Cargo.toml
Remote exception transport
Handler failures retain their original exception type, message, traceback,
exception chains, and exception groups. Runtime dispatch frames are excluded
from the user traceback, along with callers above the handler dispatch boundary.
Handler frames and their downstream calls remain visible (except for Chalk SDK
and marked generated dispatch frames); full diagnostics are retained in server
logs and internal_stacktrace.
All call modes carry a JSON payload with chalk_remote_error: 1 and an
exception object containing the ChalkException fields kind, message,
stacktrace, and internal_stacktrace. Direct calls carry the payload as the
unescaped gRPC status message; queued calls carry it in the error message. The
local async service additionally populates ChalkError.exception. This permits
existing queue transports to forward structured errors without a protobuf
migration. Clients must decode the versioned payload, not parse gRPC debug text
or classify user errors by their message. Unknown versions remain opaque.
Payloads are bounded for gRPC header limits. Truncation is marked explicitly, with complete tracebacks kept in server logs. Exception objects and locals are never pickled or sent. Chalk SDK-generated handlers identify their dispatch frames, and notebook source maps identify the deployed snapshot's lines.
Fnq integration test
On Linux, build the native extension and the paired chalk-private test harness:
# chalk-private, inside the Nix dev shell
bazel build //rust-crates/chalk/dataplane-api-server:fnq_test_server
# chalk-remote-call-python
uv pip install -e ".[dev]" redis PyJWT cryptography
FNQ_TEST_SERVER=/path/to/chalk-private/bazel-bin/rust-crates/chalk/dataplane-api-server/fnq_test_server \
REDIS_URL=redis://127.0.0.1:6379 .venv/bin/pytest tests/test_fnq_api_e2e.py -v
Use an isolated Redis instance. The tests create temporary signing keys and start
the production JWT layer and Fnq service, then exercise real native-shim execution,
lease renewal, result writes, token rotation, and environment isolation. These tests
skip unless FNQ_TEST_SERVER and REDIS_URL are set. Deploy the service before
setting CHALK_FNQ_CONSUMER_ENDPOINT on a workload.
Metadata
Release files for chalk-remote-call-python 1.10.8
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 | |
|---|---|---|---|---|
| chalk_remote_call_python-1.10.8.tar.gz | 166.2 kB | With provenance | Details |
Built distributions (wheels)
Total release size: 288.7 MB
Release files / chalk_remote_call_python-1.10.8.tar.gz
| Download URL | chalk_remote_call_python-1.10.8.tar.gz |
|---|---|
| Size | 166.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e633b2958a8e4e7a977d605f0c039e79008e21e2ad2b0590f489ce03a6230f57
|
|
BLAKE2b-256 checksum How to use checksums |
35a092b271966cd6b56f8066a027e91d96e6cb0453adea0fadadcf7cef945cef
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-win_amd64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-win_amd64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.15 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
6a2e3d2ac3be6f1c725bec49a29aef71aa2d4232a514a8264bec55c0bf90eb63
|
|
BLAKE2b-256 checksum How to use checksums |
cf0f9353931b8bf61d371d7aa80b47ed0dd1d43e3f93d8132965bce50d137f09
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-musllinux_1_2_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.15 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
3b8e7765d077e34ec2000d14e2ec1155a416f1ce2c57a20bf9e0ee1982a181dd
|
|
BLAKE2b-256 checksum How to use checksums |
8a8d005bf616922c1872d22759397337fec8ae306711fbedc915094bc25a701a
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-musllinux_1_2_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 10.4 MB |
| Tags | CPython 3.15 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
6d749a78e355ca36f21e81b2feb2425373b1f850e5f698a30f95e2f849b93576
|
|
BLAKE2b-256 checksum How to use checksums |
ca2ce2739a7c3c56ad9484223404287359be0d2bde0e08381c76b830b8b67b43
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-manylinux_2_28_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.1 MB |
| Tags | CPython 3.15 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
38603b9c3373664c1de26e9e41a607046311a1b7fa515af7857b1502ef9a85b5
|
|
BLAKE2b-256 checksum How to use checksums |
5c726a4440adae853b3861911367562066374ba78a69b1092bc80e50f523bba7
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-manylinux_2_28_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.15 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
018a602045ada54589fd7052630fd17a9f356ef697e21af3a435a0261e115a0a
|
|
BLAKE2b-256 checksum How to use checksums |
f48ea85132940c92ce6d6c6c10fa9b31e90ed3ec20b334145fecbe6a30dfd36e
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-macosx_11_0_arm64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.15 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
05b1038a30865d31f9f77147fd04512cbb09e0027c0919ee42f875248cb1790d
|
|
BLAKE2b-256 checksum How to use checksums |
0df6434ab3824afc66ae213037832a4618a22260e550520e13c812572e395114
|
| 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 / chalk_remote_call_python-1.10.8-cp315-cp315-macosx_10_15_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp315-cp315-macosx_10_15_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.15 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
5f850c875758da4386239d1e7aa4b50c98ec97ea67ead8705ae81c3ab62efffc
|
|
BLAKE2b-256 checksum How to use checksums |
658d5ebe30ba66decc59b502a741888a319332f78e9156bfa5c58c4041b0bfe5
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-win_amd64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0eee2c227526122f2b5ef6b90bcb7621214e405a3ec01705ada521e131750da8
|
|
BLAKE2b-256 checksum How to use checksums |
95784ba0d440c6dc1510894280799817e8b0d1158956c0a27ba4b90390f360a5
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
49c1f42ec380ad4e52f7dd4b63935acdf0acda1d77331b110f951072cbb4f1d4
|
|
BLAKE2b-256 checksum How to use checksums |
fc0add110ceb73f0cd56e58681f8b0dda989cc371d4633ed4270b3fe8371f5b9
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 10.4 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
2fd3de7c6f85b7c8be53dc1bc6addbbf2e4704012e8de84355df8cdfd5fa1d62
|
|
BLAKE2b-256 checksum How to use checksums |
2237c5e00d267d34e5b1a940ac1d3e4c9d9cf8b5693cc8311745efe04f7b200c
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-manylinux_2_28_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.1 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
2809ebf7d075a3d6a6e14edc95b4b5691eb8f43495ea1175dd82af1da6cd0480
|
|
BLAKE2b-256 checksum How to use checksums |
8cb9a2c8006c857c3e800682c73d7ecad62258b990b413a15c6e51dc375ff18a
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-manylinux_2_28_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.14 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
7f07d3826e5be3f46ff744538b91a159bb8f4c5982f9997a6ac394e33e33e28a
|
|
BLAKE2b-256 checksum How to use checksums |
f6c71ec30b3875d4a28425cd54db675a36452a01653f4f73731c5c952b795e1a
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-macosx_11_0_arm64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.14 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
9e7b99beac0439133743f60effc6c93064bede4a00e0b23f7f2138b9d97abc9f
|
|
BLAKE2b-256 checksum How to use checksums |
4bd1f0c93a6ff22a30e4cccae5d03a4e70dd1b27db1abd9e1d94912c506ac0a6
|
| 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 / chalk_remote_call_python-1.10.8-cp314-cp314-macosx_10_15_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp314-cp314-macosx_10_15_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.14 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
91c59bdbe36024758789c5c2c9f86c0da4abd50e159d38e42dec137d6e653994
|
|
BLAKE2b-256 checksum How to use checksums |
ac476525e0a203cb8b77d6f64e4288fb1b4a4fe0d493f985d861330c4dbc97d6
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-win_amd64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
d4f45da18889ab4e034b5b50e622d7ab23398eedb3206abcfb832723c8ee51de
|
|
BLAKE2b-256 checksum How to use checksums |
7da5f4a3b6f52f81e3ecfd5f9124eb6b0c2cabb77f81644fd183c58e5b9c1590
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
5eb0696c997f1d37a662347ea98110a43816efe47d5e76b8b95498bad53b7461
|
|
BLAKE2b-256 checksum How to use checksums |
87dc1af0ffaa4f770784eccab03e012d40f27f02ae6acfd86a8449398dbd1a7f
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 10.4 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
cb636c5e3cf2218d7788d77227b6ab7a3fe907a959a71a915d4cd5037c1326e1
|
|
BLAKE2b-256 checksum How to use checksums |
3c6a4b7d98d499d4f7e5aa57a306e4b1a8ca3518fa539c6bacaf67f8cfacaab3
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-manylinux_2_28_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.1 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
fc81c78b2fc65da94eb8c6a195773abccc5e109c5b9328f266441d8366a8590f
|
|
BLAKE2b-256 checksum How to use checksums |
0f30c99d32b4983555034d2f72ea1687ab2699f4b1c585560fd664b4565e24da
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-manylinux_2_28_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
018b7709d640de2cc78ece118703d4a43287366fb687b1253227e0429b7d280d
|
|
BLAKE2b-256 checksum How to use checksums |
4aaf2fba7ed6e6e2f196fb63fc1498b844b62dc7c4fd77d0601bfd70e5ae177b
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-macosx_11_0_arm64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.13 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1373f2f8b6ec2ae3f81454a87e7b2a4036ad2f484502684f421bce1bab630d51
|
|
BLAKE2b-256 checksum How to use checksums |
e438380778da4a0494df305a0813a2d067a30d32511b9420f89d0982398e41b8
|
| 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 / chalk_remote_call_python-1.10.8-cp313-cp313-macosx_10_13_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp313-cp313-macosx_10_13_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.13 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
bfd990d86f05858bc5d21ea3e71219103b122c892651778d14860bac6277f19f
|
|
BLAKE2b-256 checksum How to use checksums |
eeb21e076128ad71e9e6cbe859a88abd0fc9a51b7ece23f25d76f5c56abc19fb
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-win_amd64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
629e122603e774fa879710e01b5345ae68febc74690a43b05943081847c92d9e
|
|
BLAKE2b-256 checksum How to use checksums |
dbb4d4f9b54b0258b542224c7984d800b2369908d0ad2df9958e7e06a7661353
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
0ccbeb591361b75be862742b27a074cccf996204ad1cf3cd664b282de3469c89
|
|
BLAKE2b-256 checksum How to use checksums |
14d750fde51e3694d4865e8d41439089bf3074e39e19daeae0889d0645a5f28a
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 10.4 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
c74c0743a794a00991bfbb22df647d8061df70d2a8a487f779f4ca3c0b545413
|
|
BLAKE2b-256 checksum How to use checksums |
8d2827cbad8beb3d5ebc4d33b1d06110c7f3f29d4d842b3b4984d5a08920fa32
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-manylinux_2_28_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.1 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
98df667ff6e78552e9657c33f0362b3324946f29f9043c9aa2ab3137166337ce
|
|
BLAKE2b-256 checksum How to use checksums |
1b36ead668855e65958f6ee32bb56f738273938285aa32d4dfa0cb223c82dca6
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-manylinux_2_28_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
b0bcf60aa4f8090238501d5d03601b550f0a0f0e9f5ecd5956883a6b2332506a
|
|
BLAKE2b-256 checksum How to use checksums |
a07db8e8cb8637fb2386e87c2509f93f04b383459ecd1efa04c4354105dbc996
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-macosx_11_0_arm64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.12 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
845ed9c62cca4abd190e862acc6cf75dd4b7d43b05ab6db333302ecdd9a6fe0f
|
|
BLAKE2b-256 checksum How to use checksums |
ec4f9552c7e6d96793fc84a4faa42d5239c31b87f7194f51cdd6ce65b8b68910
|
| 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 / chalk_remote_call_python-1.10.8-cp312-cp312-macosx_10_13_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp312-cp312-macosx_10_13_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.12 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
92bffa73a21f81418fe082be1d3b5bd07ca67963946a3fd009ccadf4e01b9e79
|
|
BLAKE2b-256 checksum How to use checksums |
95a7dfea182bb6f45ca3b8f265dcb6aa37a7a8acec0b3b78890e108ee9d55dbf
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-win_amd64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
182f3c917860e8d8e3e6d04fd994ac8bd9cb97ab6c7f40cc030b3c86de25ab4d
|
|
BLAKE2b-256 checksum How to use checksums |
f011f4c21d1990aacad9c3db586b3ac73c68261c7b9312792aee61273caf6646
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
826686bd1db57497183f6c447b5e94965cbf3684a03db47947f6dfd335090744
|
|
BLAKE2b-256 checksum How to use checksums |
f22cf126fc86b515012feac33a40548ce967880ec42a97a96f8f19fe40505ded
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 10.4 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
614f9c7cd79692a16eae6c288ad45ff96c3a02bcd807df6e61442c106f7091be
|
|
BLAKE2b-256 checksum How to use checksums |
f0613cb944a9116a57c1c0a70e545e792792339693c71be43a717566796adc5b
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-manylinux_2_28_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.1 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
0430d6fac7f0371e8b29a2ee96a4d6c150fdd1bd63786c8eb859503998542a2f
|
|
BLAKE2b-256 checksum How to use checksums |
db991b72a07f14ed42b34e67870af17e772764aaab6ba6094f9b7266186699f7
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-manylinux_2_28_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
0302a5a250bf4f20fcb2798505a0da9e59bf1a163637c88b835364483b4e799d
|
|
BLAKE2b-256 checksum How to use checksums |
00f1b8022d8d019c659fba2a447fa278459af2a54806f6ed86afe54fa37d1bb3
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-macosx_11_0_arm64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.11 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
f1ca27a5da7632dfeec98af7505aaef027c56f15b2f3e98b4b4e6249c2206dbb
|
|
BLAKE2b-256 checksum How to use checksums |
27df5b772f80d8eabba4bd27fc8836d884d70206749d8e85e3efeb4534894f41
|
| 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 / chalk_remote_call_python-1.10.8-cp311-cp311-macosx_10_13_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp311-cp311-macosx_10_13_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.11 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
21caa09b55ef98a9738b5e2cd60b51429df6aa350d9f0ea68c084939946f48f9
|
|
BLAKE2b-256 checksum How to use checksums |
e4b80c533a0987ba77400e81800d2d105f49962fd8f79527b6165fbc2f3e16a3
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-win_amd64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
c52591da5e503fcbfbdbb7f55a63655ee5e698abae0d90e046426fa087c776bf
|
|
BLAKE2b-256 checksum How to use checksums |
d25d293d8553eea7a21f0df15eb3ed72827ffc49f617f13ef16998884246383d
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-musllinux_1_2_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.10 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
839af19f126fa42c28c062f024a57ddb3f8c2f5bb95d86ff05ed7f3f6a239c06
|
|
BLAKE2b-256 checksum How to use checksums |
b071e2b75df2b7be480a0c7c59c916b9a376fb77020012dbd58c0aa1c47cbd0a
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-musllinux_1_2_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 10.4 MB |
| Tags | CPython 3.10 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
a030e23d3ed40666ace40567c92ab1aac534b1482bc8cc57b5d0a1abe9efddca
|
|
BLAKE2b-256 checksum How to use checksums |
e05c1a4392593011fe1ffd5bd3a7f3da17c57aba4b4931a8c5ce8d658ddac078
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-manylinux_2_28_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 9.1 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
199946be3cd4742b9babc001631f7fe7076fa658c1f5e73ae35e0b89a8886b75
|
|
BLAKE2b-256 checksum How to use checksums |
65b127b3ab2fd1178daf9f3814dbd49d8c5ceea04a064bc69cb44313878a4b48
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-manylinux_2_28_aarch64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 10.3 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
6c9f0cd317213814afcf23f22e842ec675611fb6d2d16ce4f11094afa952915a
|
|
BLAKE2b-256 checksum How to use checksums |
b0c987615d87ed8e3684167e83011ca865ee481270a416f3ee5845e6b6cad28b
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-macosx_11_0_arm64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.7 MB |
| Tags | CPython 3.10 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
d86b4005f5e0f82b5ec4457a5eed14e717c66be7e4112cb4ef634cf528f7aa67
|
|
BLAKE2b-256 checksum How to use checksums |
94ab7cfb465b09db73c428140c6d54e7c0489b35522b2c76b5c46d910119ae46
|
| 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 / chalk_remote_call_python-1.10.8-cp310-cp310-macosx_10_13_x86_64.whl
| Download URL | chalk_remote_call_python-1.10.8-cp310-cp310-macosx_10_13_x86_64.whl |
|---|---|
| Size | 2.8 MB |
| Tags | CPython 3.10 macOS 10.13+ x86-64 |
|
SHA-256 checksum How to use checksums |
429a357227b0e1ab19f5796600538187b4c9c02669f141847801702a0d437a7b
|
|
BLAKE2b-256 checksum How to use checksums |
3268bfee39d4571f86b26330ee7b84f8d45b904071af9de7ebf36f6c24ad4a14
|
| 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 chalk-remote-call-python 1.10.8
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 43 files in this release have been uploaded with provenance metadata.
Attestation for chalk_remote_call_python-1.10.8.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.
