This release is a pre-release and may not be stable for production use.
raydriver
Rust-native machine drivers for Rayforge, exposed to Python via PyO3.
Currently this provides a full port of Rayforge's advanced GRBL serial driver: character-counting flow control, handshake and status polling, interactive command queue, job streaming with stall detection and deadlock recovery, cancel/safety-shutdown semantics, settings and WCS access, and probe cycles. Dialects (command templates) remain data owned by Rayforge and are passed in resolved form.
CLI
The raydriver command runs G-code against a real device with live
progress, or against the built-in firmware emulator for hardware-free
dry runs:
raydriver run job.gcode --port /dev/ttyUSB0 --baudrate 115200
raydriver run job.gcode --emulator # no hardware needed
raydriver status --port /dev/ttyUSB0 --seconds 5
While a job runs, raydriver run shows acknowledged lines, a
progress bar, the device state, machine position, feed rate and ETA;
Ctrl-C cancels the job and runs the safety shutdown.
Releases
Releasing mirrors the Raygeo flow:
- Configure a PyPI trusted publisher for this repository once
(owner
barebaric, reporaydriver, workflowrelease.yml, environmentpypi). gh release create v0.1.0 --title "v0.1.0" --generate-notes
The Build and Publish workflow then stamps the version from the
tag, builds wheels (Linux/Windows/macOS) and an sdist, publishes to
PyPI via OIDC, and attaches the artifacts to the GitHub release.
Development
make venv && source .venv/bin/activate
make dev # build + install (do this before testing)
make test # pytest suite (all tests are Python-based)
make check # lint + test
Usage
import asyncio
from raydriver.grbl import GrblSession, SessionEvent
session = GrblSession(
config={"port": "/dev/ttyUSB0", "baudrate": 115200},
dialect={
"home_all": "$H",
"home_axis": "$H{axis_letter}",
"clear_alarm": "$X",
"laser_on": "M4 S{power:.0f}",
"laser_off": "M5",
},
event_callback=on_event,
)
def on_event(event: SessionEvent):
match event:
case SessionEvent.StateChanged():
print("device state:", event.state.status.name)
case SessionEvent.ConnectionStatusChanged(status=status):
print("connection:", status)
case SessionEvent.RawRx(line=line):
print("<<", line)
case SessionEvent.RawTx(line=line):
print(">>", line)
async def main():
await session.connect()
print(await session.execute_interactive_command("$I"))
await session.disconnect()
asyncio.run(main())
Metadata
Release files for raydriver 1.0.0b4
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 | Actions |
|---|---|---|---|---|
| raydriver-1.0.0b4.tar.gz | 132.7 kB | With provenance | Details for raydriver-1.0.0b4.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| raydriver-1.0.0b4-cp311-abi3-win_amd64.whl | CPython 3.11 | abi3 | Windows x86-64 | Details for raydriver-1.0.0b4-cp311-abi3-win_amd64.whl |
| raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.34+ x86-64 | Details for raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_x86_64.whl |
| raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_aarch64.whl | CPython 3.11 | abi3 | Linux glibc 2.34+ ARM64 | Details for raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_aarch64.whl |
| raydriver-1.0.0b4-cp311-abi3-macosx_11_0_arm64.whl | CPython 3.11 | abi3 | macOS 11.0+ ARM64 | Details for raydriver-1.0.0b4-cp311-abi3-macosx_11_0_arm64.whl |
| raydriver-1.0.0b4-cp311-abi3-macosx_10_12_x86_64.whl | CPython 3.11 | abi3 | macOS 10.12+ x86-64 | Details for raydriver-1.0.0b4-cp311-abi3-macosx_10_12_x86_64.whl |
Total release size: 10.6 MB
Release files / raydriver-1.0.0b4.tar.gz
| Download URL | raydriver-1.0.0b4.tar.gz |
|---|---|
| Size | 132.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
221451d5d52271ff5082282c933301fc6ad5d49640890517bb6e9e8cdb9c079a
|
|
BLAKE2b-256 checksum How to use checksums |
3ebe96a162ca783bfdeda15178f7b79bfe31f97bcc71dc36784f0be58b846fde
|
| 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 31, 2026.
Transparency logRelease files / raydriver-1.0.0b4-cp311-abi3-win_amd64.whl
| Download URL | raydriver-1.0.0b4-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
2aad47cbb06ba150537ecc4b00e51624e27be97db91daab2a68817f9e369ee7a
|
|
BLAKE2b-256 checksum How to use checksums |
3332ba2a69c9d3dc8a35596d1108c5c88e6dfbc74b7a9bd5546f5a3af7be1157
|
| 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 31, 2026.
Transparency logRelease files / raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_x86_64.whl
| Download URL | raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
20d2a08868cefcfdf023f279559b2c53a489f8760628f0b5be12e58bc3ce30e6
|
|
BLAKE2b-256 checksum How to use checksums |
567490e4454ecb8ebd37e7b48cf596bd072f0c91fc7c416483aacde6d0bf416f
|
| 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 31, 2026.
Transparency logRelease files / raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_aarch64.whl
| Download URL | raydriver-1.0.0b4-cp311-abi3-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 2.2 MB |
| Tags | CPython 3.11 Linux glibc 2.34+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
02b314824be2d36f8d4e6dfd6a81db8713cebdae1d355edaf4155e2597e9e8c6
|
|
BLAKE2b-256 checksum How to use checksums |
af4cd1869a4ee029e896e3fe1d58a6e7833735828522fd742efc0758666dc6d1
|
| 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 31, 2026.
Transparency logRelease files / raydriver-1.0.0b4-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | raydriver-1.0.0b4-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
c2778e8653f37f87138569a1d8bce0c33eaaedacbf04a3e39816af450eb22e8d
|
|
BLAKE2b-256 checksum How to use checksums |
91acfaf21e2594f65f10e3fbd91e23ddc8c8220ddb39cc3b88259b457a326c36
|
| 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 31, 2026.
Transparency logRelease files / raydriver-1.0.0b4-cp311-abi3-macosx_10_12_x86_64.whl
| Download URL | raydriver-1.0.0b4-cp311-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 2.0 MB |
| Tags | CPython 3.11 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
3470f6a26d14e6c199e49f5826d8635ad0cc82956ea509d84baeb70a9ef93b15
|
|
BLAKE2b-256 checksum How to use checksums |
2e4b7e78d8d6792271ea82f2f4393f389e65696e7358d7003086a4f1f500225e
|
| 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 31, 2026.
Transparency logSecurity for raydriver 1.0.0b4
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 6 files in this release have been uploaded with provenance metadata.
Attestation for raydriver-1.0.0b4.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 31, 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.