RESPONDPY
🐍 Welcome to RESPOND for Python! 🐍 This repository acts as a set of python bindings for the Syndemics Lab's RESPOND model. As such, it is simply a set of wrappers and helper functions for ease of use in various lab projects. Our project can be installed from PyPI or built locally.
RESPOND
RESPOND is a simulation model developed by the Syndemics Lab at Boston Medical Center to study the various cost-effectiveness impacts of different treatment options for substance use disorders (SUD). While originally built to study opioid use disorder (OUD), RESPOND is a Markov model with the ability to scale to encompass various drug use behaviors and treatment approaches or venues. This repository adds bindings and helper functions to easily work with SQLite. The original RESPOND model is written in R and C++ and can be found on GitHub.
Pybind11
This tool makes use of the popular tool Pybind11. From here, we expose bindings for users to connect to via Python.
Logging Across C++ and Python
respondpy now exposes RESPOND logging through a top-level module,
respondpy.logging, so Python and C++ can write to the same logger/file
without reimplementing logging behavior.
from pathlib import Path
import respondpy as rpy
from respondpy.data import Input
base = Path("/path/to/respond-input")
log_name = "respond"
log_file = "respond.log"
# Input can initialize the logger through the C++ backend.
input_data = Input(path=base, log_name=log_name, log_file=log_file)
# Python-side logging uses the same RESPOND logger backend.
rpy.logging.log_info(log_name, "Loading input complete")
rpy.logging.log_warning(log_name, "Using fallback parameter for cohort 3")
rpy.logging.flush_all_loggers()
To support concurrent logging from multiple models/threads to one file, prefer the shared sink APIs exposed by the same module:
import respondpy as rpy
rpy.logging.create_shared_file_sink("respond.log")
rpy.logging.create_shared_logger("respond")
Building and Installing
The bindings are available on PyPI! They can be installed via pip install respondpy.
If you want to build the project locally, we make use of scikit-build-core along with CMake to build the library. To build locally, you can clone the repository here.
git clone git@github.com:SyndemicsLab/respondpy.git
uv sync
uv build
This results in a wheel and tar.gz being placed in a dist/ directory. From here, we use uv to include it in other projects. Future work would be to allow for building device independent wheels and publishing to PyPI where we could install anywhere.
Supported OSes
We are currently working on supporting as many OSes as possible. As these are bindings for a C++ project, we are limited in our capacity. For the moment, we are generating Linux and Windows builds for Python versions >= 3.11. No Mac builds are available at present.
Binding Parity Checklist
Use this checklist when updating bindings, stubs, or API docs.
- Run smoke tests:
uv run pytest -m smoke - Runtime vs stubs parity:
- Confirm pybind runtime signatures and return shapes match
.pyiannotations. - Confirm enum members and bound method names match stub names exactly.
- Confirm overload behavior matches typed expectations.
- Confirm pybind runtime signatures and return shapes match
- Runtime vs docs parity:
- Confirm binding docstrings describe actual runtime return types and side effects.
- Confirm parameter defaults in docs match bound defaults.
- Expected-failure messaging parity:
- Confirm incorrect arguments raise errors with stable, informative message patterns.
- Prefer regex pattern assertions in tests over exact full-message equality.
- Smoke coverage scope:
- Runtime binding smoke lives in
tests/test_smoke_bindings_runtime.py. - Stub smoke via
mypyin pytest lives intests/test_typing_stubs_mypy.py.
- Runtime binding smoke lives in
Metadata
Release files for respondpy 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| respondpy-0.3.4.tar.gz | 184.0 kB | Details |
Built distributions (wheels)
Total release size: 50.7 MB
Release files / respondpy-0.3.4.tar.gz
| Download URL | respondpy-0.3.4.tar.gz |
|---|---|
| Size | 184.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
41870ed57111d4121cdd3ac75d14137b64c19dd4c3731e96bdfa34cc95073e25
|
|
BLAKE2b-256 checksum How to use checksums |
d59f7a6101e22a677d375257720003be32afa3ce4560d1d74f70712b81267d57
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp314-cp314-win_arm64.whl
| Download URL | respondpy-0.3.4-cp314-cp314-win_arm64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.14 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
877686a7e47bce601eadac1aebfb7285eae34b2b96b4fe00c11aeb554998f806
|
|
BLAKE2b-256 checksum How to use checksums |
08fdab5433e8e3beb3694d2daf29207ce75c7edd57592e06c2b0c6ae4345762b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp314-cp314-win_amd64.whl
| Download URL | respondpy-0.3.4-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
3a94693e47c38e8e0009969000442ea992ca4ee1366186520ceb234189055a1b
|
|
BLAKE2b-256 checksum How to use checksums |
0869ed8a0ef349b18ea383af84378834002ddb163f575b47d34799d07075d2d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | respondpy-0.3.4-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
468a6fd19dfe9c1556b7bfce2a13b97ba29f5bc3eb177bf74178c19c8efb58ef
|
|
BLAKE2b-256 checksum How to use checksums |
5b83099b389cd454e1b9ac68375975da29001149389265a3b1296180be8f8b95
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | respondpy-0.3.4-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
88574dc7a1d8abeeb0bd81e34befa8e3881a29db8f8729bcd782fb212a194b8b
|
|
BLAKE2b-256 checksum How to use checksums |
3a179cc62250a9cd02b3e4ca29b35905eae4b99f9682023ea8d75a2d8c3177b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | respondpy-0.3.4-cp314-cp314-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ac3c102ef70d6c9db5198675128c0bb974d41591600d7feddcafeaa78f951bb7
|
|
BLAKE2b-256 checksum How to use checksums |
878d4e1afb75c0194acddc2c45b4b23455e67459b6d4fb3ee8ebd128f94d4257
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | respondpy-0.3.4-cp314-cp314-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.14 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
a8c323feee7ae3692ab09ba95045fb2430d4ebbc8673eee7944babe59dcac8f0
|
|
BLAKE2b-256 checksum How to use checksums |
22189da9c92ea9e76dda11782ed8498ce975d3e3063c115aa9a46aa069f730d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp313-cp313-win_arm64.whl
| Download URL | respondpy-0.3.4-cp313-cp313-win_arm64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.13 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
0afa4751f99cd7207e961c3537bdde23025c5d71d640a483c1238f01a3bb1381
|
|
BLAKE2b-256 checksum How to use checksums |
c510d1250477d3ff9295a4768b41e28a190f76dad8f32ea5947540fb0b312cfd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp313-cp313-win_amd64.whl
| Download URL | respondpy-0.3.4-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
06a044a71102589a759f49da571044d2ee44f64fb0acc080e379eccb1c9a4f54
|
|
BLAKE2b-256 checksum How to use checksums |
23df3d49b6720e130106963a3ea026d7904b68e4331888f9e22d7d2d3d1d699e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | respondpy-0.3.4-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
0d5a5c911d14dcc2ff5520a5ce6464f07c463086a93c13be5c324b52a6f50b20
|
|
BLAKE2b-256 checksum How to use checksums |
1aef4d4a3e9b37bce705b7eb867e6ff23d8d77e170545e1d7b4e060e0fa3f728
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | respondpy-0.3.4-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
c62432896759c68254ac5f65939e51bc76d9ee90b98e178a3c3f96846e29ab3c
|
|
BLAKE2b-256 checksum How to use checksums |
8c480b3215b60e1aab3a09a7d588efe00b5dad27814a8afeac62b2c59b55910d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | respondpy-0.3.4-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b8c5517079435d2d6b21dffeed21869d6ce5912d9aa2f1b4b4455948428943f4
|
|
BLAKE2b-256 checksum How to use checksums |
5767a316c1971bbd15f6a4d8f60bc0255d4c99c3da2792bd66efddcce99aba82
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | respondpy-0.3.4-cp313-cp313-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.13 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
4d102dc3c19868cd5e696af8a0524bd89a0b1959c911a841f2721985605c97fb
|
|
BLAKE2b-256 checksum How to use checksums |
3b36bad70ea53e46e70eacd72dfb3a2afed42dff8b097420e92c7233dc7cc312
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp312-cp312-win_arm64.whl
| Download URL | respondpy-0.3.4-cp312-cp312-win_arm64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.12 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
f000bd022262aa0a9a473bd7a27a6b43df50a2da62b4e9868766a63aa2f1a565
|
|
BLAKE2b-256 checksum How to use checksums |
662ad0c352cae687418c7d447ceb941e36ee98a9ae5e7943c4943bd75ac44a60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp312-cp312-win_amd64.whl
| Download URL | respondpy-0.3.4-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
14c11d9cccca5413a42500eeac63c3d8364cc8f0b29aad69382c52512c7b7d69
|
|
BLAKE2b-256 checksum How to use checksums |
a57aed01214672e5488ed90471069f775de86085e56be8c738784979d20b2f26
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | respondpy-0.3.4-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
acfe0efd1cf9227db26c591180bbdac24f271d2f24e2ae60f292d0ca9c1ee516
|
|
BLAKE2b-256 checksum How to use checksums |
22cf3137ffa58dc1bf93eec2c7c160df202aaf5cd974ecd87b3216b479050f59
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | respondpy-0.3.4-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
301ed5f4f4a34676c927468e84cb40f2f5f186249d03e010a33d2bcebedae8e5
|
|
BLAKE2b-256 checksum How to use checksums |
cafd095430034c1a2a66f285bc57901e2b30ec0a6c2fc19e6516911b83d4bb2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | respondpy-0.3.4-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
86d11853a264431da8fb8e870ef417cfbe6bb473459c51d661424f66e5a4c3eb
|
|
BLAKE2b-256 checksum How to use checksums |
5906fcb28e564c55f06bd54f218ffef51665ed36def21a6d0b7aa57320ed32fb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | respondpy-0.3.4-cp312-cp312-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.12 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
cf3a0149da801b67c5211967e2183ac69410ed8f0f81315f6f3c30b23bfa71ac
|
|
BLAKE2b-256 checksum How to use checksums |
065b2cfc9b012889df9d300fe9623b1341d917a94f7e431059294f7155c73707
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp311-cp311-win_arm64.whl
| Download URL | respondpy-0.3.4-cp311-cp311-win_arm64.whl |
|---|---|
| Size | 2.6 MB |
| Tags | CPython 3.11 Windows ARM64 |
|
SHA-256 checksum How to use checksums |
bb6b1d5c70f6bdf46a2dacf1bceede0af333b1e10e5b0fdc95542f0904d05215
|
|
BLAKE2b-256 checksum How to use checksums |
7825b97e4ae8d8c08053755a75b653087b4e89eddd7eb07660b13a3e26e78523
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp311-cp311-win_amd64.whl
| Download URL | respondpy-0.3.4-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 2.5 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
90499052d33b5a1e5e38299cde83efd6921ce74ce68854e02e913943990956cf
|
|
BLAKE2b-256 checksum How to use checksums |
4f38913b1840e80fbdedf11c1ca70c5cf559a18da546e00260a35b900e505531
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp311-cp311-musllinux_1_2_x86_64.whl
| Download URL | respondpy-0.3.4-cp311-cp311-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 2.4 MB |
| Tags | CPython 3.11 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
3f180c96cad529eaa26de0a9abf625d9e50f5ac1e04de4bae1cd67f6b0904407
|
|
BLAKE2b-256 checksum How to use checksums |
aa9d93ca5eedaad03070e1fe7d5e92f1de70e85160aec6af8f56a4b511192b2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp311-cp311-musllinux_1_2_aarch64.whl
| Download URL | respondpy-0.3.4-cp311-cp311-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 2.3 MB |
| Tags | CPython 3.11 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
570b2b1f30c3db498b554525b95a83c97273acb7539a7e938f423d1685ba8926
|
|
BLAKE2b-256 checksum How to use checksums |
c4383e3ce31bd4799e8db1a47d6223f9f3d41ce4937d49887e08ff428dbabcea
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | respondpy-0.3.4-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 1.4 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
ee22d9625bb206960388bbbc68b455aae78682445b80228aa3bb8e9e7d5b43d3
|
|
BLAKE2b-256 checksum How to use checksums |
0fd274d08ea01465b9a812303b4c60b4cb275096daac86a9f5b59b5b760c2f66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / respondpy-0.3.4-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl
| Download URL | respondpy-0.3.4-cp311-cp311-manylinux_2_26_aarch64.manylinux_2_28_aarch64.whl |
|---|---|
| Size | 1.3 MB |
| Tags | CPython 3.11 Linux glibc 2.26+ ARM64 Linux glibc 2.28+ ARM64 |
|
SHA-256 checksum How to use checksums |
ae34c99d7e0ee4959386fe5164650c574b894b2e6aa668ac1dff79418c2de5c9
|
|
BLAKE2b-256 checksum How to use checksums |
78a58ef8e28c57e377ebb2a732b0b952930d6b1f9e6ca2a2b7f287a352a892c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency log