visio-schema
The wire contract for the Visio sensor ecosystem: the generated protobuf
message bindings plus a small, hand-written framing codec, packaged so you can
read a live device or a recording with one pip install. It is the single
source of truth for what Visio data looks like on the wire; the transport,
bus, and recording stack live in a separate layer.
Imported as visio_schema. Full docs, the wire spec, and C++ sources are in the
GitHub repository.
Install
pip install visio-schema
One install includes MCAP read/write (read_mcap / McapWriter) and the
visio-display live viewer — no extras to choose. Released wheels (Linux
manylinux_2_28 x86_64, macOS universal2, CPython 3.10–3.13) bundle an optional
native reader for higher throughput. If no wheel matches your platform, the sdist
installs a pure-Python reader with identical behavior — only throughput differs.
Quickstart
from visio_schema import read_serial, read_mcap, message_class
# live device -> (Message, Channel) rows
for msg, ch in read_serial("/dev/ttyACM0"):
cls = message_class(ch.schema_name) # resolve the payload type
payload = cls.FromString(msg.payload)
print(ch.topic, payload)
# replay a recording
for msg, ch in read_mcap("run.mcap"):
...
Send commands and read replies with serial_endpoint(...) + command_message.
See usage.md
for the three end-to-end recipes.
visio-display viewer
The package installs a visio-display console command that reads a live device
(serial or TCP) or replays an MCAP, and fans it out to a live
Foxglove WebSocket, a live Rerun
viewer, and/or an MCAP recording:
visio-display --serial /dev/ttyACM0 --rerun
visio-display --tcp my-device.local --foxglove
visio-display --mcap-in run.mcap --rerun
# also runnable as: python -m visio_schema.display
License
MIT — see LICENSE.
Metadata
Release files for visio-schema 0.4.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 | |
|---|---|---|---|
| visio_schema-0.4.2.tar.gz | 302.7 kB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| visio_schema-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.13 | CPython 3.13 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| visio_schema-0.4.2-cp313-cp313-macosx_11_0_universal2.whl | CPython 3.13 | CPython 3.13 | macOS 11.0+ universal2 (ARM64, x86-64) | Details |
| visio_schema-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.12 | CPython 3.12 | Linux glibc 2.28+ x86-64, Linux glibc 2.27+ x86-64 | Details |
| visio_schema-0.4.2-cp312-cp312-macosx_11_0_universal2.whl | CPython 3.12 | CPython 3.12 | macOS 11.0+ universal2 (ARM64, x86-64) | Details |
| visio_schema-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.11 | CPython 3.11 | Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 | Details |
| visio_schema-0.4.2-cp311-cp311-macosx_11_0_universal2.whl | CPython 3.11 | CPython 3.11 | macOS 11.0+ universal2 (ARM64, x86-64) | Details |
| visio_schema-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl | CPython 3.10 | CPython 3.10 | Linux glibc 2.27+ x86-64, Linux glibc 2.28+ x86-64 | Details |
| visio_schema-0.4.2-cp310-cp310-macosx_11_0_universal2.whl | CPython 3.10 | CPython 3.10 | macOS 11.0+ universal2 (ARM64, x86-64) | Details |
Total release size: 10.9 MB
Release files / visio_schema-0.4.2.tar.gz
| Download URL | visio_schema-0.4.2.tar.gz |
|---|---|
| Size | 302.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8e182f6b2dba7a49fe85ae5680f1cf4708e6708fd663016be3bb89f401874be3
|
|
BLAKE2b-256 checksum How to use checksums |
dfc1a1f8acc034bf11f0fad7deac7d550a3097b07742984dd3f4107f51980854
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | visio_schema-0.4.2-cp313-cp313-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.13 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
470b067104c3f522eec8bf1f104c1b4b3cf5e0af9786790d09a4c3cffcf52bbf
|
|
BLAKE2b-256 checksum How to use checksums |
89f62d91c47be1b1585b41dd1d61d77d64c9c463b3e9855f09ea21866fb28dbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp313-cp313-macosx_11_0_universal2.whl
| Download URL | visio_schema-0.4.2-cp313-cp313-macosx_11_0_universal2.whl |
|---|---|
| Size | 503.2 kB |
| Tags | CPython 3.13 macOS 11.0+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
c546a7a3472647d0aef7b829e7ce3141e2b94ee00a055ebf68cf48def4d2bdb4
|
|
BLAKE2b-256 checksum How to use checksums |
96b2aceed547d5c5e3744e8a68ff0cf7818b059d917bb91e7d73f1450c6bab6e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | visio_schema-0.4.2-cp312-cp312-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.12 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
c2de26130ac089a3addbde3bec5052d324ad4f333ba4eaadc29276b6acdb9fb9
|
|
BLAKE2b-256 checksum How to use checksums |
8c552797946577c4a7c11fa156cef9c77bc8e81a719878c0e628fdb6e7f2b9c3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp312-cp312-macosx_11_0_universal2.whl
| Download URL | visio_schema-0.4.2-cp312-cp312-macosx_11_0_universal2.whl |
|---|---|
| Size | 503.2 kB |
| Tags | CPython 3.12 macOS 11.0+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
d2461d8a5b5d94078280e2ce5e4efaad768fc654f05928af8a7c8c0b902532e5
|
|
BLAKE2b-256 checksum How to use checksums |
ae6026c49d103bbba8e06ae319546d044800d41f8d553fa5f998af0a61d96371
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | visio_schema-0.4.2-cp311-cp311-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.11 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
b66d2e597b41215b6b6a2d42c66eab966395e5a1755c576fe7ea82272fe0de50
|
|
BLAKE2b-256 checksum How to use checksums |
a416c24aabc9faf7ab065697442b7f3dcfad8be757530724eea674c7d4fd97b3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp311-cp311-macosx_11_0_universal2.whl
| Download URL | visio_schema-0.4.2-cp311-cp311-macosx_11_0_universal2.whl |
|---|---|
| Size | 498.0 kB |
| Tags | CPython 3.11 macOS 11.0+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
4e7c04538ea44db717537794eb94378f5dd4ea74e76245dd4cc8e624434c87f3
|
|
BLAKE2b-256 checksum How to use checksums |
6168cf454a003baccdfebc4404745298b956c56ec8056b0f5f2d59de610fa524
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl
| Download URL | visio_schema-0.4.2-cp310-cp310-manylinux_2_27_x86_64.manylinux_2_28_x86_64.whl |
|---|---|
| Size | 2.1 MB |
| Tags | CPython 3.10 Linux glibc 2.27+ x86-64 Linux glibc 2.28+ x86-64 |
|
SHA-256 checksum How to use checksums |
40858ffa1b14375bb7e70e159cd24c7cd62d879736e6f2a07a04848c22335fb1
|
|
BLAKE2b-256 checksum How to use checksums |
1574bfce5d09c316d7041e6d28a8d750a3d10e60bb1bb045097c9d826fe63526
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency logRelease files / visio_schema-0.4.2-cp310-cp310-macosx_11_0_universal2.whl
| Download URL | visio_schema-0.4.2-cp310-cp310-macosx_11_0_universal2.whl |
|---|---|
| Size | 495.2 kB |
| Tags | CPython 3.10 macOS 11.0+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
4d667d7101f6ed2ceee8ad4dc9b25a87c45a8d951b6edc5fa6b8233deab69032
|
|
BLAKE2b-256 checksum How to use checksums |
b99af1db21be180cd01d59267626cbaa6260081b35276f15ae0d05f0564ff96b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jul 10, 2026.
Transparency log