Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

rp2040py

license pypi version python versions Pre-commit Test MicroPython Releases Test Pi Pico SDK coverage

Raspberry Pi Pico (RP2040) Emulator in Python — started as a port of rp2040js, now grown into its own CLI/SDK toolkit around it (see Differences from upstream rp2040js below). It blinks, runs native code, and even the MicroPython REPL!

See docs/reference/porting-checklist.md for the file-by-file port status against upstream rp2040js.

Quick start

pip install rp2040py
rp2040py micropython          # boots real MicroPython firmware, drops you into its REPL (Ctrl+X to quit)
rp2040py micropython -c "print(1 + 1)"   # or run one command non-interactively and exit

That's it — no manual firmware download, no board wiring. Everything below is depth: more firmware families (CircuitPython, Kaluma), WiFi, filesystems, a programmatic API, and how to add your own boards/devices. See Run the demo project for the full CLI, or jump straight to External devices & custom boards if you're here to extend it.

Table of Contents

Installation

pip install rp2040py

or, with uv:

uv add rp2040py       # into a project
uv tool install rp2040py   # as a standalone CLI tool
uvx rp2040py ...           # run without installing at all

Any of these gives you the rp2040py console script (python -m rp2040py works identically), so the emulator is runnable without a git checkout - see Run the demo project below for the checkout-equivalent commands.

Shell completions

rp2040py install-completion sets up tab completion for every subcommand and flag (--board, --log-level, --littlefs, ...) in Bash or Zsh, via argcomplete:

rp2040py install-completion
# then open a new shell, or:
source ~/.bashrc   # or ~/.zshrc

This appends the shell's register-python-argcomplete hook to ~/.bashrc/~/.zshrc (detected from $SHELL) - a one-time setup step, not something run on every invocation.

Use in CI (GitHub Action)

This repository is itself a composite GitHub Action (action.yml at the repo root, ready for GitHub Marketplace publishing): it installs rp2040py as a standalone tool (via uv tool install) so later steps in the same job can run the rp2040py command directly. Unlike the plain Installation instructions above, it installs from the action's own checkout (github.action_path) rather than from PyPI - the version that runs is exactly the ref the caller pins below, with no separate package index to keep in sync with the action tag:

- uses: o-murphy/rp2040py@v0.3.3   # pin a released tag; @main tracks the default branch
  with:
    python_version: "pypy-3.10"   # optional: interpreter for rp2040py's own tool env; defaults to PyPy
    extras: "fs"                  # optional: comma-separated extras to install; defaults to "fs"
- run: rp2040py micropython -c "print(1 + 1)"

The root-level uses: o-murphy/rp2040py@<tag> form above needs v0.3.2 or newer - that release moved action.yml to the repo root and added the extras input; older tags are reachable only through the previous o-murphy/rp2040py/.github/actions/setup-rp2040py@<ref> path.

See Used by below for a real project consuming this action from outside this repo (this repository's own CI tests the local checkout directly via uv sync/uv run, so its workflows under .github/workflows/ aren't examples of consuming the published action).

Run the demo project

The commands below assume rp2040py is installed (pip install rp2040py / uv add rp2040py / uv tool install rp2040py, or run ad hoc with uvx rp2040py ...). From a checkout of this repo instead, each maps 1:1 onto uv run python demo/*.py (demo/*.py are thin wrappers around the same src/rp2040py/cli code):

rp2040py subcommand Checkout equivalent
rp2040py run ... uv run python demo/emulator_run.py ...
rp2040py micropython ... uv run python demo/micropython_run.py ...
rp2040py kaluma ... uv run python demo/kaluma_run.py ...
rp2040py bench ... uv run python demo/benchmark.py ...

Two demos have no CLI equivalent because they emulate hardware rather than run firmware: the Waveshare 2.9″ e-Paper panel (demo/eink_run.py) and the RP2040-LCD-0.96's onboard ST7735S (demo/lcd_run.py). demo/README.md shows what both actually draw.

--board {pico,pico_w} (default pico) is available on all four and picks which board's fixed extras get attached alongside the RP2040 itself - the onboard LED and the BOOTSEL button on both, plus an emulated CYW43439 WiFi/Bluetooth chip on pico_w; see WiFi (Pico W / CYW43439) below.

Native code

You'd need to get hello_uart.hex by building it from the pico-examples repo, then copy it to the rp2040py root directory and run:

rp2040py run
# or, without installing:
uvx rp2040py run

You can also specify the path to the image on the command line and/or load a UF2 image:

rp2040py run --image ./my-pico-project.uf2

A GDB server will be available on port 3333, and the data written to UART0 will be printed to the console.

MicroPython code

No manual download needed: just run

rp2040py micropython
# or, without installing:
uvx rp2040py micropython

and enjoy the MicroPython REPL! Quit the REPL with Ctrl+X. The first run fetches the recommended MicroPython build (1.29.0, currently) from micropython.org into ~/.cache/rp2040py and reuses that cached file afterwards (falls back to the current directory if the cache directory isn't writable). Any recent release boots to the REPL quickly in the emulator (see the benchmark below).

A different version, a local UF2 file, or a CircuitPython version (--circuitpython, see below) can be loaded by supplying the --image option - a known version tag (1.28.0), or a path to a UF2 file already on disk:

rp2040py micropython --image 1.28.0
rp2040py micropython --image my_image.uf2

A GDB server on port 3333 can be enabled by specifying the --gdb flag:

rp2040py micropython --gdb

For using the MicroPython demo code in tests, --expect-text can come in handy: it will look for the given text in the serial output and exit with code 0 if found, or 1 if not found. It's repeatable (--expect-text foo --expect-text bar stops once both have appeared, on any line, not necessarily the same one or in that order) and, with --expect-regex, each --expect-text value is matched as a Python re pattern (via re.search) instead of a plain substring. You can find an example in the MicroPython CI test.

For one-shot, non-interactive runs (like micropython's own CLI), pass one of -c <command>, -m <module>, or a script <filename> - mutually exclusive, matching [-c <command> | -m <module> | <filename>]. Instead of dropping into the REPL, rp2040py boots the device, runs it via the raw-REPL protocol, prints its stdout/stderr, and exits with the device's exit status (0 on success, 1 if it raised):

rp2040py micropython -c "print(1 + 1)"
rp2040py micropython -m sys
rp2040py micropython path/to/script.py

mpremote

--tcp-port <port> serves the console over a plain TCP socket instead of this process's own stdio, so mpremote can connect directly via pySerial's built-in socket:// support - no client-side patching needed:

rp2040py micropython --tcp-port 4321
# in another terminal:
mpremote connect socket://127.0.0.1:4321 exec "print(1 + 1)"
mpremote connect socket://127.0.0.1:4321 fs cp your_script.py :main.py

--pty (POSIX only) is the alternative - a real pseudo-terminal, which additionally supports mpremote's own bare interactive REPL (rp2040py mpremote, a thin proxy subcommand, gets that working over --tcp-port too, patching around an upstream mpremote bug).

See docs/reference/mpremote.md for the full picture: connection details for both flags, the proxy and the bug it patches around, how to quit the emulator when mpremote owns the console, and exactly which mpremote commands are verified working where.

Filesystem support and WiFi both work here too, and cover MicroPython/CircuitPython/Kaluma in one place below - see Filesystem support and WiFi (Pico W / CYW43439).

CircuitPython code

To run the CircuitPython demo, follow the directions above for MicroPython but add --circuitpython:

rp2040py micropython --circuitpython

and start the CircuitPython REPL! As with MicroPython, the firmware (10.2.1 by default) is downloaded automatically on first use; a different version or a local file can be given via --image (e.g. --image 8.0.2 or a path to an already-downloaded UF2). The rest of the experience is the same as the MicroPython demo (Ctrl+X to exit, the --gdb option, etc). Filesystem support (a FAT12 image, not littlefs) and WiFi both work here too - see Filesystem support and WiFi (Pico W / CYW43439) below, which cover all three firmware families in one place.

Kaluma

rp2040py's USB/CDC emulation isn't MicroPython-specific - any firmware presenting a CDC-ACM serial console works the same way underneath. The kaluma subcommand runs Kaluma (a JavaScript runtime for RP2040), verified against 1.2.1 - it boots, USB enumerates, and evaluates real JS at its REPL prompt (e.g. sending 1+1 gets back 2):

rp2040py kaluma
# or, without installing:
uvx rp2040py kaluma
rp2040py kaluma --image 1.2.1
rp2040py kaluma --image my_kaluma_image.uf2

As with micropython, missing firmware is downloaded automatically (1.2.1 by default - the newest release still shipping a plain, non--w, RP2040 pico build; 1.3.0+ only ships pico2/pico2-w). Ctrl+X to exit, same as the MicroPython demo. Unlike micropython, kaluma is interactive-only - Kaluma has no raw-REPL-equivalent protocol, so there's no -c/-m/<filename>.

An optional <script.js> positional stages a local file into Kaluma's "user program" flash region before boot - the same one kaluma flash <file> writes to on real hardware, which Kaluma auto-executes on every boot:

rp2040py kaluma your_script.js

--board pico_w works here too - Kaluma's own require('wifi') scans, joins, gets a DHCP lease, and opens real net.Socket connections to the internet through the same bridge described under WiFi (Pico W / CYW43439) below (tests/kaluma/main-cyw43.js is a runnable example), and filesystem support is covered under Filesystem support below too, alongside MicroPython/CircuitPython's.

Give it a few real seconds after connecting before expecting output - like MicroPython, booting real firmware through an interpreted emulator takes actual wall-clock time (JerryScript engine init, then running your script), not something --expect-text needs to work around, just something to expect if driving this non-interactively.

--tcp-port <port>/--pty also work here, same as micropython - see mpremote above (that section is mpremote-specific, but the underlying mechanism, a plain socket/pty serving the console instead of this process's own stdio, is not).

Kaluma prints its "Welcome to Kaluma" banner exactly once, right at boot - but that's before the emulated USB-CDC connection to the host is actually up, so (same as real hardware racing a host terminal that isn't already attached - Kaluma's own docs: "if you cannot see the prompt, press Enter several times") those bytes are typically gone by the time anything's listening. kaluma doesn't send anything to work around this - type .hi yourself at the prompt to reprint the same banner on demand if you need to see it; if you're scripting against a device's output instead of typing at it interactively, stage a <script.js> and match against its output, which isn't racy (see the Kaluma CI test, which does exactly that).

Filesystem support

mklittlefs builds a writeable LittleFS-formatted image on the host (needs the optional fs extra: pip install rp2040py[fs] / uv sync --extra fs) - shared by MicroPython and Kaluma, which both boot from real littlefs flash:

rp2040py mklittlefs -o littlefs.img your_main.py your.py files.py here.py --main your_main.py

Every file keeps its own basename; --main marks one as auto-run on boot (omit it for a filesystem with no auto-run script, or omit files entirely for an empty formatted image). Always builds fresh - pass -f/--force to overwrite an existing --output. --target {micropython,circuitpython,kaluma} presets --block-size/--block-count to a known firmware's own layout instead of spelling them out by hand (mutually exclusive with passing them explicitly - the three differ, see the per-firmware notes below). --disk-version {2.0,2.1} selects the littlefs on-disk format (defaults to 2.0: MicroPython <=1.21's bundled littlefs can only mount 2.0, 1.28's reads both - see docs/records/0003).

  • MicroPython: --littlefs path/to/littlefs.img mounts it and auto-runs main.py if present (silently skipped, not an error, if it isn't - but never loaded at all unless --littlefs is given explicitly). The filesystem is writeable at runtime - os/rp2.Flash calls go through a real JEDEC SPI-NOR command emulation in the SSI peripheral (RPSSI), the same one real flash hardware uses.

  • Kaluma: its own pluggable littlefs-backed filesystem (see its docs) lives in a different, fixed 512K flash region (4096-byte blocks) than the <script.js> user-program staging area above, with no auto-run semantics of its own - plain storage, accessed from JS via require('fs'). Pass it via --littlefs explicitly (never picked up implicitly, even from a kaluma_littlefs.img in the current directory):

    rp2040py mklittlefs -o kaluma_littlefs.img --target kaluma your_script.js
    rp2040py kaluma --littlefs kaluma_littlefs.img
    

    Without a valid image, board.js's unconditional mount-at-startup logs cosmetic Bad block/ Superblock ... unwritable/No space left on device errors against unformatted flash - Kaluma catches and prints them without aborting, so boot and <script.js> auto-run continue normally.

  • CircuitPython: a FAT12 image instead of littlefs - build one with truncate/mkfs.vfat (not mklittlefs) and pass it via --fat12 (no default, never picked up implicitly):

    truncate fat12.img -s 1M && mkfs.vfat -F12 -S512 fat12.img
    mkdir fat12 && sudo mount -o loop fat12.img fat12/ && sudo cp code.py fat12/ && sudo umount fat12/
    rp2040py micropython --circuitpython --fat12 fat12.img
    

    It can also write its own drive, which is usually the easier route: storage.remount('/', readonly=False) at the REPL, then plain open()/write(). On real hardware that raises while a USB host holds the mass-storage lock; this emulator claims only the CDC interface, so the lock is free and the firmware builds the volume itself - long names and subdirectories included. Restart it afterwards (Ctrl-B then Ctrl-D at the console) to make CircuitPython re-run code.py, and --dump-fs if you want to keep the image. demo/lcd_run.py --code and demo/wifi_lcd_run.py both work this way; see docs/records/0087.

The format is a property of the firmware family, not a choice, so the two flags are mutually exclusive and family-checked: --fat12 needs --circuitpython, --littlefs needs its absence, and the wrong one is a startup error rather than a flag that is quietly ignored (a --fat12 image.img run without --circuitpython used to boot with no filesystem at all and no hint as to why). A named image that doesn't exist is still skipped silently - that is about the file, not the flag.

--dump-fs <path> dumps a device's filesystem flash region back out to a local file on exit (Ctrl+X, --expect-text, or the end of a run) - the same layout --littlefs/--fat12 reads back in, so it round-trips for persistence across runs. Works for all three families - littlefs for MicroPython and Kaluma, FAT12 for CircuitPython; MicroPython additionally supports scripting it non-interactively via -c/-m/<filename> (see demo/mklittlefs_dump.py, which builds such a script from local files) - Kaluma has no non-interactive exec mode, so use require('fs') at its REPL instead. This makes --dump-fs a littlefs-python-free alternative to mklittlefs on either firmware: boot against blank flash, write files the normal way, dump the result - built by that firmware's own bundled littlefs, not a separately-installed library.

WiFi (Pico W / CYW43439)

--board pico_w (default: pico, any firmware) attaches an emulated CYW43439 - the WiFi/Bluetooth chip on a real Pico W - over the same gSPI bus real firmware drives it through. network.WLAN (MicroPython), wifi/socketpool (CircuitPython), and require('wifi')/net (Kaluma) all work against it - three independent network stacks over one bus, none of them needing anything CYW43-specific from the emulator:

rp2040py micropython --board pico_w

nic.active(True), nic.scan(), and nic.connect(ssid, key) all complete, answered by a fixed fake "RP2040PY-GUEST" access point built into the emulation. The association is fake, but the network behind it is real - a NAT bridge gives the guest a DHCP lease, answers its ARP, and splices its TCP connections and UDP datagrams onto real sockets on your machine, so code running on the emulated Pico W reaches the actual internet. Live-boot verified against real, unmodified MicroPython firmware on both 1.23.0 and 1.28.0:

import network, socket, mip, ntptime

nic = network.WLAN(network.WLAN.IF_STA)
nic.active(True)
print(nic.scan())  # [(b'RP2040PY-GUEST', ...)]
nic.connect("RP2040PY-GUEST", "key")  # any password is accepted
print(nic.isconnected(), nic.ipconfig("addr4"))  # True ('10.0.0.2', '255.255.255.0')

s = socket.socket()  # real TCP, out through your host's network
s.connect(("1.1.1.1", 80))
s.send(b"GET / HTTP/1.0\r\n\r\n")
print(s.recv(64))  # b'HTTP/1.1 301 Moved Permanently\r\n...'

mip.install("os-path")  # real DNS + a real HTTPS download
ntptime.settime()  # real NTP, sets the emulated RTC
nic.disconnect()  # link really goes down: isconnected() -> False, status() -> 0

TLS works through the same path (the reflector relays bytes without inspecting them), and so do WebSockets over both ws:// and wss://. CircuitPython (tests/circuitpython/main-cyw43.py) and Kaluma (tests/kaluma/main-cyw43.js) have their own runnable examples; CircuitPython additionally enforces WPA2's 8-64 character passphrase rule client-side, so the password you pass must be at least 8 characters even though the emulated AP accepts anything.

What is not emulated, so you don't discover it the hard way:

  • The AP is a fixture. scan() always returns the one fake "RP2040PY-GUEST" network, any password "succeeds," and there's no hidden-SSID or auth-failure path to test against.
  • No AP mode (network.WLAN.IF_AP), no IPv6, and one guest only (the guest/gateway IP and MAC are fixed constants, with no config surface yet).
  • No flow-control backpressure from the real destination onto the guest: the emulator always advertises a fixed TCP receive window, so a guest that outran a slow destination would grow the host process's socket buffer rather than being told to slow down. An emulated Cortex-M0 can't realistically outrun a real socket, which is why this hasn't mattered in practice.

See docs/records/0027-cyw43-wifi.md for what's emulated at the gSPI/SDPCM protocol level and docs/records/0048-cyw43-nat-reflector.md for the network bridge (how the reflector works, and the full list of what's still open).

Bootrom revisions

run, micropython, kaluma, and bench all boot a fixed bootrom (B1, bundled - no download needed) by default. --bootrom picks a different one: a b0/b1/b2 version tag (downloaded automatically from Raspberry Pi's pico-bootrom-rp2040 releases and cached locally, same as --image), or a local .elf/.bin path:

rp2040py micropython --bootrom b2
rp2040py micropython --bootrom path/to/custom.elf

Raspberry Pi only publishes .elf for each revision - pyelftools (a normal dependency, not an extra: it's a pure-Python wheel with no platform-specific build to justify gating it) parses out the ROM image on the fly, no separate conversion step needed. A local .bin (e.g. produced with objcopy -O binary) is loaded directly with no parsing at all.

Library API

Everything above is the CLI, but the emulator is also usable programmatically - e.g. to run code against a device and check its output the way Thonny does over a real serial port, from a test suite or another tool. rp2040py.device.MicroPythonDevice boots a board and lets you run code on it via the same raw-REPL protocol mpremote run/tools/pyboard.py use, interrupting anything already running on the device first (e.g. an auto-run main.py from a littlefs image). board is keyword-only and is the only board-related argument - a resolved BoardSpec carrying its own firmware image, never a board-name string or a separate image= kwarg; see docs/reference/external-devices-and-boards.md for building one of your own.

asyncio, via astart()/aexec()/aexec_file(), entered as an async with context manager:

import asyncio
from rp2040py.boards import BOARDS, resolve_firmware
from rp2040py.device import MicroPythonDevice


async def main():
    # Downloads and caches the family's default firmware; pass a third argument
    # ("1.23.0", a local .uf2 path, a URL) to pin a different one.
    board = resolve_firmware(BOARDS["pico"], "micropython")
    async with MicroPythonDevice(board=board) as device:
        stdout, stderr = await device.aexec("print(1 + 1)")
        assert stdout == b"2\r\n"

        stdout, stderr = await device.aexec_file("my_script.py")


asyncio.run(main())

Callback style, via exec_async()'s concurrent.futures.Future - no separate API needed, Future.add_done_callback() does this out of the box. Requires the device already started (astart()/start_async() first, or already inside async with):

def on_done(future):
    stdout, stderr = future.result()
    print(stdout.decode())


device.exec_async("print(1 + 1)").add_done_callback(on_done)

Both share one asyncio.Lock per device: since the device only has a single REPL channel and can't run two exec()s at once, calling exec_async()/aexec() again before a previous call finishes doesn't raise, it just queues behind it and runs once its turn comes. This is exactly what powers the CLI's own micropython -c/-m/<filename> batch mode - it's a caller of this same API, not a separate implementation. start_async()/astart()/stop() are available directly if you want more control over the lifecycle than the context manager gives you - stop() itself stays a plain synchronous call.

External devices & custom boards

Beyond the built-in --board {pico,pico_w} presets, the emulator has a real extension point for hardware it doesn't model out of the box:

  • ExternalDevice (rp2040py.external.device) - a device implements attach(rp2040) and gets wired up via attach_external_devices(). Devices already shipping in-tree this way: the onboard LED, the BOOTSEL button, the RESET button (the RUN pin), a generic button/key, the CYW43439 WiFi chip behind pico_w, a Waveshare 2.9″ e-Paper panel, an ST7735S TFT controller, and a WS2812/WS2812B "NeoPixel" RGB LED.
  • boards.BoardSpec (what --board itself resolves to internally) - a public dataclass you build your own instance of: your own device mix on an existing firmware family, or a fully custom board with its own firmware and flash layout. Hand it to any Device class (board=...) or the CLI (--board-spec target:attr / RP2040PY_BOARD_SPEC, on run/micropython/kaluma/ mklittlefs). A board declares its firmware as data - a firmware dict keyed by family (micropython/circuitpython/kaluma), each entry a tag→URL-or-local-path map plus that family's flash layout - so one file covers one board for every firmware that runs on it, downloads nothing when imported, and works with --image/--fetch-fw-only exactly as --board does.

Adding your own

docs/reference/external-devices-and-boards.md is the full how-to: worked examples for both a new device and a new board, the attach-timing rule, and the caveats worth knowing before you start. If you're working in Claude Code, the external-devices-and-boards skill turns that into a step-by-step execution checklist (which template to copy, which test proves what, and the "3g rule" - every electrical fact cited to a real upstream source, never guessed).

Ready-made example boards

19 worked --board-spec targets for real third-party hardware live in boards/ - every number sourced from that board's own upstream firmware config (never guessed), live-boot-verified against real firmware. See docs/reference/external-devices-and-boards.md for the full list with what each one demonstrates. Screenshots of what the two emulated display panels actually draw are in demo/README.md; see docs/records/0049/ 0059 for the design history behind the extension points themselves.

Performance

The emulator core is also available as a compiled extension (rp2040py.native): the Cortex-M0+ core, the bus, the clock and every peripheral (SIO, timer, pins, PIO, DMA, SSI, UART, SPI, I2C, ADC, PWM, USB, the clock tree, CYW43 gSPI, ...) are C++17 behind thin Cython shells (the C++ core even boots MicroPython on its own, with no Python), and the batch execution loop runs entirely in C++ (docs/records/0096-cpp-mcu-core.md). Against the pure-Python build that is roughly 100x to the first line of MicroPython's output (table in the tip above), and it is where rp2040py sits ahead of rp2040js. The pure-Python implementations stay in the tree as the reference the native blocks are tested against, and as the fallback.

This is on by default and needs nothing from you: pip install rp2040py builds it automatically when a C compiler is available (prebuilt wheels are published for common platforms, so most installs don't even need one) and falls back to the identical pure-Python implementation otherwise

  • correctness is the same either way, just the speed differs. A couple of environment variables exist for cases where you want to control this explicitly:

  • RP2040PY_SKIP_CYTHON=1 - force the pure-Python implementation at runtime, even if the compiled extension is installed (e.g. to rule out a native-specific issue).

  • RP2040PY_SKIP_NATIVE_BUILD=1 - skip compiling the extension at build time, for a deliberately pure-Python install/wheel.

CoreMark: a busy core, not boot-and-idle

The speed-up quoted above is for a boot that mostly idles, where the emulator can jump over the time nothing happens. A core that never stops is the other end: CoreMark (the single-core v1.0.0 build) keeps the CPU running for about 12 s of simulated chip time, so the wall time is a direct measure of instruction throughput. demo/coremark_single_thread.py runs it and stops on the result line.

Variant Wall time Speed vs. the chip Iterations/Sec
CPython + native extension 32 s ~0.4x 248.46
PyPy 3.10, pure Python 171 s ~0.07x 248.46
CPython, pure Python 5349 s (89 min) ~0.002x 248.46
  • The score is the same in all three (1.99 CoreMark/MHz at 125 MHz), so the builds agree on what the firmware computes.
  • The native extension is ~167x faster than pure CPython and ~5x faster than PyPy; PyPy is ~31x faster than pure CPython.
  • Two cores. demo/coremark_dual_core.py builds a patched CoreMark that really uses both cores (the upstream release with a second core, v1.0.7, does not benchmark anything) and runs it: a valid result with equal CRCs on both cores, 491 CoreMark against 237 for the single-core build. One thread executes the two cores in turn, so the wall time per simulated second is ~2.2x that of one busy core: in a cloud container the native build ran one busy core at ~0.62x of real time and two at ~0.28x.
  • On a busy core the native build runs at roughly 0.4x of real time. The "~100x" above is a figure for idle time, not for instruction throughput - do not read it as the speed of a busy core.
  • One run per variant on one machine, not an average: treat the factors as an order of magnitude. The pure-CPython run was cut at the result line (--expect-regex), so its log has no "Correct operation validated" line; the score and the total time are there, and the validation is confirmed for the native and PyPy runs.

Differences from upstream rp2040js

rp2040py started as a straight port of rp2040js - the core CPU/peripheral emulation still tracks it closely, and docs/reference/porting-checklist.md keeps a file-by-file checklist of that. But it's grown well past a 1:1 translation into its own toolkit with no rp2040js equivalent, built around actually running real firmware from a shell rather than embedding the emulator as a library (rp2040js's own primary use case, e.g. inside Wokwi):

  • A real packaged CLI - rp2040py/python -m rp2040py, installable via pip/uv, not just a checkout-only demo/*.ts script. Firmware (MicroPython/CircuitPython/Kaluma) is auto-downloaded and cached by version tag instead of needing to be fetched and placed by hand.
  • A real, writeable filesystem: RPSSI (the SSI peripheral MicroPython/CircuitPython's os/rp2.Flash calls go through to erase/program flash) implements the actual JEDEC SPI-NOR command set (WREN/WRDI, status/JEDEC-ID reads, page program, sector/block erase) - the same commands real flash hardware understands - not just a register stub. rp2040js has the same gap MicroPython/CircuitPython on rp2040py used to have (see docs/records/0008-ssi-flash-write.md's "SSI flash-write support"): on-device open(path, "w")/os.remove()/... genuinely persist to the emulated flash now, instead of raising/no-opping against an unimplemented peripheral.
  • A filesystem toolkit: mklittlefs builds a littlefs image on the host (needs littlefs-python, the optional fs extra); --dump-fs builds one without that dependency instead, by writing files to a booted device's real filesystem the normal way and reading the resulting flash region back out - see mpremote and Filesystem support above.
  • A programmatic device API (rp2040py.device.MicroPythonDevice/KalumaDevice) for driving a booted device from another Python program over the raw-REPL protocol (device.exec("print(1+1)")) - the same API micropython -c/-m/<filename> and --tcp-port themselves are built on, not a separate implementation. --tcp-port/--pty in particular let any serial-oriented external tool - mpremote chief among them, including its own bare interactive REPL via rp2040py mpremote (see mpremote) - drive the emulator over a real socket or pty, something rp2040js has no analogue for at all (no pty/socket-backed USB-CDC passthrough anywhere in its source, only stdio-driven demo scripts).
  • Broader firmware coverage: MicroPython, CircuitPython, and Kaluma (a second, independent USB-CDC-console JS runtime for RP2040 - unrelated to rp2040js despite both being JS) all boot and run against this emulator; a built-in GDB server (--gdb) works against any of them.
  • A real chip reset, from every trigger that has one: rp2040js's own RPWatchdog.onWatchdogTrigger (src/peripherals/watchdog.ts) defaults to logging "Watchdog triggered, but no reset handler provided" and does nothing else - the emulated CPU spins forever waiting for a reset that never happens. Here machine.reset()/machine.bootloader() work, and they are one caller of a single reset owner rather than the only path: a RESET button (external/reset_button.py - a real RUN-pin level, so holding it holds the chip in reset) and a host-side device.ahard_reset() reach the same sequence. What that sequence covers is the blocks a real reset covers - pads, IO, SIO, clocks, UART/SPI/I2C/PIO/TIMER/ADC/USB/RTC/BUSCTRL and the XIP domain - gated by PSM.WDSEL/RESETS.WDSEL exactly as hardware gates them, so a GPIO the guest left driving is released and WiFi comes back up on a Pico W. Flash/filesystem content and every externally-referenced peripheral object's identity survive (the reset is in place, never a reconstruction), and the firmware reports the right machine.reset_cause() / microcontroller.cpu.reset_reason for the trigger that actually fired. mpremote reset/ mpremote bootloader (the latter performs the same reset rather than entering actual BOOTSEL mode, which isn't implemented) both return promptly instead of hanging.
  • Configurable bootrom revision (--bootrom b0/b1/b2, or a local .elf/.bin) - see Bootrom revisions below - auto-downloaded and cached the same way firmware images are. rp2040js ships exactly one hardcoded bootrom build (demo/bootrom.ts, revision B1), with no way to select a different revision at all.
  • Both cores (multicore_launch_core1(), MicroPython's _thread, CoreMark on two cores), with a two-core lockstep oracle holding the compiled and the pure-Python loops identical - see the note at the top and docs/records/0104.
  • An optional native-compiled backend (rp2040py.native, Cython) for when pure-Python instruction dispatch is the bottleneck - see Performance above - alongside a pure-Python universal wheel for environments that can't load compiled extensions at all (e.g. Pythonista, see Installation).
  • Pico W / CYW43439 WiFi emulation (--board pico_w) - real network.WLAN calls (active()/scan()/connect()) against a real, unmodified MicroPython firmware's CYW43439 driver are answered at the actual gSPI/SDPCM protocol level, not stubbed out, and a NAT bridge carries the guest's TCP/UDP traffic onto your host's real network (socket, mip.install() and ntptime all reach the actual internet) - something rp2040js has no equivalent of at all (no --board concept, no WiFi chip emulation). See WiFi (Pico W / CYW43439) above.
  • A real extension point for third-party hardware (ExternalDevice/boards.BoardSpec) - rp2040js has no board or device abstraction at all, only whatever's hardcoded into its own demo scripts. rp2040py ships 19 worked --board-spec examples for real vendor boards (WeAct Studio, four Waveshare boards, VCC-GND Studio, three Adafruit boards, McHobby's PYBStick26, Machdyne, nullbits, Pimoroni, Seeed Studio, SparkFun, two 0xCB boards), every electrical fact cited to that board's own upstream firmware source and live-boot-verified, plus a documented how-to for writing your own. See External devices & custom boards above.

See docs/reference/porting-checklist.md#known-differences-from-rp2040js for the exhaustive, file-level breakdown (including behavioral divergences found while porting, not just added features).

Used by

  • ballistics-lab/micropython-bclibc — tests its RP2040 usermod/natmod builds in CI by actually booting real firmware through this emulator (uses: o-murphy/rp2040py@<tag>, see Use in CI above), not just compiling it.

Learn more

License

Released under the MIT license. Copyright (c) 2021, Uri Shaked. Copyright (c) 2026, Dmytro Yaroshenko.

Metadata

Release files for rp2040py 1.0.0b1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rp2040py 1.0.0b1
File Size Uploaded Provenance Actions
rp2040py-1.0.0b1.tar.gz 2.5 MB With provenance Details for rp2040py-1.0.0b1.tar.gz

Built distributions (wheels)

Table of built distributions (wheels) for rp2040py 1.0.0b1
File Actions
rp2040py-1.0.0b1-py3-none-any.whl Python 3 none any Details for rp2040py-1.0.0b1-py3-none-any.whl
rp2040py-1.0.0b1-cp315-cp315t-win_arm64.whl CPython 3.15 CPython 3.15 free-threading Windows ARM64 Details for rp2040py-1.0.0b1-cp315-cp315t-win_arm64.whl
rp2040py-1.0.0b1-cp315-cp315t-win_amd64.whl CPython 3.15 CPython 3.15 free-threading Windows x86-64 Details for rp2040py-1.0.0b1-cp315-cp315t-win_amd64.whl
rp2040py-1.0.0b1-cp315-cp315t-win32.whl CPython 3.15 CPython 3.15 free-threading Windows x86-32 Details for rp2040py-1.0.0b1-cp315-cp315t-win32.whl
rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64 Details for rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_x86_64.whl
rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_i686.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-32 Details for rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_i686.whl
rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_armv7l.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARMv7l Details for rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_armv7l.whl
rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64 Details for rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_aarch64.whl
rp2040py-1.0.0b1-cp315-cp315t-manylinux_2_26_i686.manylinux_2_28_i686.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.26+ x86-32, Linux glibc 2.28+ x86-32 Details for rp2040py-1.0.0b1-cp315-cp315t-manylinux_2_26_i686.manylinux_2_28_i686.whl
rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64, Linux glibc 2.28+ x86-64 Details for rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARMv7l, Linux glibc 2.31+ ARMv7l Details for rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.15 CPython 3.15 free-threading Linux glibc 2.28+ ARM64, Linux glibc 2.17+ ARM64 Details for rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
rp2040py-1.0.0b1-cp315-cp315t-macosx_11_0_arm64.whl CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64 Details for rp2040py-1.0.0b1-cp315-cp315t-macosx_11_0_arm64.whl
rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_x86_64.whl CPython 3.15 CPython 3.15 free-threading macOS 10.15+ x86-64 Details for rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_x86_64.whl
rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_universal2.whl CPython 3.15 CPython 3.15 free-threading macOS 10.15+ universal2 (ARM64, x86-64) Details for rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_universal2.whl
rp2040py-1.0.0b1-cp315-cp315-pyemscripten_2026_5_wasm32.whl CPython 3.15 CPython 3.15 PyEmscripten 2026.5+ WebAssembly Details for rp2040py-1.0.0b1-cp315-cp315-pyemscripten_2026_5_wasm32.whl
rp2040py-1.0.0b1-cp315-cp315-android_24_x86_64.whl CPython 3.15 CPython 3.15 Android API level 24+ x86-64 Details for rp2040py-1.0.0b1-cp315-cp315-android_24_x86_64.whl
rp2040py-1.0.0b1-cp315-cp315-android_24_arm64_v8a.whl CPython 3.15 CPython 3.15 Android API level 24+ ARM64 v8a Details for rp2040py-1.0.0b1-cp315-cp315-android_24_arm64_v8a.whl
rp2040py-1.0.0b1-cp314-cp314t-win_arm64.whl CPython 3.14 CPython 3.14 free-threading Windows ARM64 Details for rp2040py-1.0.0b1-cp314-cp314t-win_arm64.whl
rp2040py-1.0.0b1-cp314-cp314t-win_amd64.whl CPython 3.14 CPython 3.14 free-threading Windows x86-64 Details for rp2040py-1.0.0b1-cp314-cp314t-win_amd64.whl
rp2040py-1.0.0b1-cp314-cp314t-win32.whl CPython 3.14 CPython 3.14 free-threading Windows x86-32 Details for rp2040py-1.0.0b1-cp314-cp314t-win32.whl
rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64 Details for rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_x86_64.whl
rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_i686.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-32 Details for rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_i686.whl
rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_armv7l.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARMv7l Details for rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_armv7l.whl
rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64 Details for rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_aarch64.whl
rp2040py-1.0.0b1-cp314-cp314t-manylinux_2_26_i686.manylinux_2_28_i686.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-32, Linux glibc 2.26+ x86-32 Details for rp2040py-1.0.0b1-cp314-cp314t-manylinux_2_26_i686.manylinux_2_28_i686.whl
rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.31+ ARMv7l, Linux glibc 2.17+ ARMv7l Details for rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
rp2040py-1.0.0b1-cp314-cp314t-macosx_11_0_arm64.whl CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64 Details for rp2040py-1.0.0b1-cp314-cp314t-macosx_11_0_arm64.whl
rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_x86_64.whl CPython 3.14 CPython 3.14 free-threading macOS 10.15+ x86-64 Details for rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_x86_64.whl
rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_universal2.whl CPython 3.14 CPython 3.14 free-threading macOS 10.15+ universal2 (ARM64, x86-64) Details for rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_universal2.whl
rp2040py-1.0.0b1-cp314-cp314-pyemscripten_2026_0_wasm32.whl CPython 3.14 CPython 3.14 PyEmscripten 2026.0+ WebAssembly Details for rp2040py-1.0.0b1-cp314-cp314-pyemscripten_2026_0_wasm32.whl
rp2040py-1.0.0b1-cp314-cp314-android_24_x86_64.whl CPython 3.14 CPython 3.14 Android API level 24+ x86-64 Details for rp2040py-1.0.0b1-cp314-cp314-android_24_x86_64.whl
rp2040py-1.0.0b1-cp314-cp314-android_24_arm64_v8a.whl CPython 3.14 CPython 3.14 Android API level 24+ ARM64 v8a Details for rp2040py-1.0.0b1-cp314-cp314-android_24_arm64_v8a.whl
rp2040py-1.0.0b1-cp313-cp313-pyemscripten_2025_0_wasm32.whl CPython 3.13 CPython 3.13 PyEmscripten 2025.0+ WebAssembly Details for rp2040py-1.0.0b1-cp313-cp313-pyemscripten_2025_0_wasm32.whl
rp2040py-1.0.0b1-cp313-cp313-android_24_x86_64.whl CPython 3.13 CPython 3.13 Android API level 24+ x86-64 Details for rp2040py-1.0.0b1-cp313-cp313-android_24_x86_64.whl
rp2040py-1.0.0b1-cp313-cp313-android_24_arm64_v8a.whl CPython 3.13 CPython 3.13 Android API level 24+ ARM64 v8a Details for rp2040py-1.0.0b1-cp313-cp313-android_24_arm64_v8a.whl
rp2040py-1.0.0b1-cp311-abi3-win_arm64.whl CPython 3.11 abi3 Windows ARM64 Details for rp2040py-1.0.0b1-cp311-abi3-win_arm64.whl
rp2040py-1.0.0b1-cp311-abi3-win_amd64.whl CPython 3.11 abi3 Windows x86-64 Details for rp2040py-1.0.0b1-cp311-abi3-win_amd64.whl
rp2040py-1.0.0b1-cp311-abi3-win32.whl CPython 3.11 abi3 Windows x86-32 Details for rp2040py-1.0.0b1-cp311-abi3-win32.whl
rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_x86_64.whl CPython 3.11 abi3 Linux musl 1.2+ x86-64 Details for rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_x86_64.whl
rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_i686.whl CPython 3.11 abi3 Linux musl 1.2+ x86-32 Details for rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_i686.whl
rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_armv7l.whl CPython 3.11 abi3 Linux musl 1.2+ ARMv7l Details for rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_armv7l.whl
rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_aarch64.whl CPython 3.11 abi3 Linux musl 1.2+ ARM64 Details for rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_aarch64.whl
rp2040py-1.0.0b1-cp311-abi3-manylinux_2_26_i686.manylinux_2_28_i686.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-32, Linux glibc 2.26+ x86-32 Details for rp2040py-1.0.0b1-cp311-abi3-manylinux_2_26_i686.manylinux_2_28_i686.whl
rp2040py-1.0.0b1-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.11 abi3 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for rp2040py-1.0.0b1-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
rp2040py-1.0.0b1-cp311-abi3-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl CPython 3.11 abi3 Linux glibc 2.31+ ARMv7l, Linux glibc 2.17+ ARMv7l Details for rp2040py-1.0.0b1-cp311-abi3-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
rp2040py-1.0.0b1-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.11 abi3 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for rp2040py-1.0.0b1-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
rp2040py-1.0.0b1-cp311-abi3-macosx_11_0_arm64.whl CPython 3.11 abi3 macOS 11.0+ ARM64 Details for rp2040py-1.0.0b1-cp311-abi3-macosx_11_0_arm64.whl
rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_x86_64.whl CPython 3.11 abi3 macOS 10.9+ x86-64 Details for rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_x86_64.whl
rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_universal2.whl CPython 3.11 abi3 macOS 10.9+ universal2 (ARM64, x86-64) Details for rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_universal2.whl
rp2040py-1.0.0b1-cp310-cp310-win_arm64.whl CPython 3.10 CPython 3.10 Windows ARM64 Details for rp2040py-1.0.0b1-cp310-cp310-win_arm64.whl
rp2040py-1.0.0b1-cp310-cp310-win_amd64.whl CPython 3.10 CPython 3.10 Windows x86-64 Details for rp2040py-1.0.0b1-cp310-cp310-win_amd64.whl
rp2040py-1.0.0b1-cp310-cp310-win32.whl CPython 3.10 CPython 3.10 Windows x86-32 Details for rp2040py-1.0.0b1-cp310-cp310-win32.whl
rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_x86_64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-64 Details for rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_x86_64.whl
rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_i686.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ x86-32 Details for rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_i686.whl
rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_armv7l.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARMv7l Details for rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_armv7l.whl
rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_aarch64.whl CPython 3.10 CPython 3.10 Linux musl 1.2+ ARM64 Details for rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_aarch64.whl
rp2040py-1.0.0b1-cp310-cp310-manylinux_2_26_i686.manylinux_2_28_i686.whl CPython 3.10 CPython 3.10 Linux glibc 2.26+ x86-32, Linux glibc 2.28+ x86-32 Details for rp2040py-1.0.0b1-cp310-cp310-manylinux_2_26_i686.manylinux_2_28_i686.whl
rp2040py-1.0.0b1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl CPython 3.10 CPython 3.10 Linux glibc 2.28+ x86-64, Linux glibc 2.17+ x86-64 Details for rp2040py-1.0.0b1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
rp2040py-1.0.0b1-cp310-cp310-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl CPython 3.10 CPython 3.10 Linux glibc 2.31+ ARMv7l, Linux glibc 2.17+ ARMv7l Details for rp2040py-1.0.0b1-cp310-cp310-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
rp2040py-1.0.0b1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl CPython 3.10 CPython 3.10 Linux glibc 2.17+ ARM64, Linux glibc 2.28+ ARM64 Details for rp2040py-1.0.0b1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
rp2040py-1.0.0b1-cp310-cp310-macosx_11_0_arm64.whl CPython 3.10 CPython 3.10 macOS 11.0+ ARM64 Details for rp2040py-1.0.0b1-cp310-cp310-macosx_11_0_arm64.whl
rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_x86_64.whl CPython 3.10 CPython 3.10 macOS 10.9+ x86-64 Details for rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_x86_64.whl
rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_universal2.whl CPython 3.10 CPython 3.10 macOS 10.9+ universal2 (ARM64, x86-64) Details for rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_universal2.whl

Total release size: 506.9 MB

Release files / rp2040py-1.0.0b1.tar.gz

Download URL rp2040py-1.0.0b1.tar.gz
Size 2.5 MB
Tags Source
SHA-256 checksum
How to use checksums
45917588ba81fded055e90958be6e139beed666d43abd886698db5eda51f6a99
BLAKE2b-256 checksum
How to use checksums
aa547cf212eaac876eb623186fcabe0d083ae540511f10a41fba010635f28738
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-py3-none-any.whl

Download URL rp2040py-1.0.0b1-py3-none-any.whl
Size 881.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d21672b795d7d159479ea013b9999258952434758965b6847c437a7dfe6b6e6a
BLAKE2b-256 checksum
How to use checksums
97b54de9c6646f5db243cd8450081b1eb4c97b3b50c78f702aae83bc3ba85c54
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-win_arm64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-win_arm64.whl
Size 7.0 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows ARM64
SHA-256 checksum
How to use checksums
b2e546b4d751e1f6bc84d721139cd8e42d96239edb8a5ecb333e45fe8d258e3e
BLAKE2b-256 checksum
How to use checksums
7f4fae9c56d9ef9dbf125ab8248875a5b956f313951293815eb345a180a2c926
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-win_amd64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-win_amd64.whl
Size 7.2 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
818a8bf9d13bd91d5ab048a6637dd17e93785f265521ca8d8d18d02f60c3d554
BLAKE2b-256 checksum
How to use checksums
acfb6b6986365df8b8d41cef4fe70a7c1aee29e0eb5592d34da0bc2c46173711
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-win32.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-win32.whl
Size 6.9 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-32
SHA-256 checksum
How to use checksums
8bf87d27406ff59c4bfa637e4ab754df3e8ddc48b672e84f107f09cb5aacc6c7
BLAKE2b-256 checksum
How to use checksums
0bbd37ea6ea7b0ec2deaa64e58bd46da13a8eebd90dc6363f0201aad185547b0
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_x86_64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_x86_64.whl
Size 8.6 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
30211bcb53d66e415095c6f81b1c2554a5789b88032bec561aa5b3df716aabbb
BLAKE2b-256 checksum
How to use checksums
23828ddf44e032ac43bfc3a24b3ec67f8854f2b49fd3764f3d610304f534108a
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_i686.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_i686.whl
Size 8.7 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-32
SHA-256 checksum
How to use checksums
c1fd81d13eb4b95151689b3733a65c91224b7bcd5fcbfbdf9a2df17658b7d57d
BLAKE2b-256 checksum
How to use checksums
877f3ec69dc5a2c5309f629d435d512788533636f50024e6bf4273afdcbe398c
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_armv7l.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_armv7l.whl
Size 8.3 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARMv7l
SHA-256 checksum
How to use checksums
bd5e9701449381a605da02327fbf1cf3932959dc378bd920b0b47730c0b29569
BLAKE2b-256 checksum
How to use checksums
c2bb729f00f960cbfe32d6c01cf0da9a24da7b8d2fa91dec9c0038c39690f1fe
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_aarch64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-musllinux_1_2_aarch64.whl
Size 8.5 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
c6ee9a34c17479e034179a97b40b7e1bf6937f63791196b04f4cc5345e77e097
BLAKE2b-256 checksum
How to use checksums
66896a2958b6742d13b502c1cd752020ac71594432b8a7ce5cacc90810985c3e
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-manylinux_2_26_i686.manylinux_2_28_i686.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 7.5 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.26+ x86-32 Linux glibc 2.28+ x86-32
SHA-256 checksum
How to use checksums
de8b02068c0c8e9bfa9915c63e42659940e088a5cf25f8777f7f1c5df66660b7
BLAKE2b-256 checksum
How to use checksums
2b34d8d25fd96b8905b9ac73e55aca2ae0ad0799f2564a9240d98d8f322506df
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.6 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
e5f7a4f895a27bcb2cdff98e3db16187c25c6dbb7aaaf7009ba7059780ecd3a5
BLAKE2b-256 checksum
How to use checksums
482b9c90abffe095ac47207f26aec55dc007e6e82ce60c9fa91d7a924b411f6c
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 7.4 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARMv7l Linux glibc 2.31+ ARMv7l
SHA-256 checksum
How to use checksums
751b0dd97e1ad8ef30c18656d710b6a073e346d3635ca3b2fccc1e997de76b09
BLAKE2b-256 checksum
How to use checksums
e8b9d31d9afb58bd07991f4deaa0c5b12d99139005b170fb85d730d92b6a5ff3
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 7.5 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
ab0312749c87a783f05dff9cda988afc5c5c62c8456dd00aba30d90561ee320a
BLAKE2b-256 checksum
How to use checksums
afd128f34527a5cdd9a16456235e3c278b6e4f502b40faf4833b85d5830302ff
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-macosx_11_0_arm64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-macosx_11_0_arm64.whl
Size 7.6 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
658a2659abe2a50b32206de80bcd1a228a5fd25aa72de8da8fe7ac7849dd057d
BLAKE2b-256 checksum
How to use checksums
4ecd66873a6a00cded01d1d48279d9ba2d1c03245f033bc2b927e18e5916fdcf
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_x86_64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_x86_64.whl
Size 7.6 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
7d0a46c9c7c49ffb8582f70a94876ebec9e82c500f512c054c942308481c80a2
BLAKE2b-256 checksum
How to use checksums
6bce59b0386eab6c9a4e69393613fc6a16522fbad38cca022071e7e890912a01
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_universal2.whl

Download URL rp2040py-1.0.0b1-cp315-cp315t-macosx_10_15_universal2.whl
Size 10.0 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 10.15+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
252c009f172bcf840cab353e082b6311b36177cb3fdb58cb73bcb75d745f39a1
BLAKE2b-256 checksum
How to use checksums
2c90e35aeabf804aae779ccf8f9497ff816286d753f2dd66c43ddc97794d80b8
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315-pyemscripten_2026_5_wasm32.whl

Download URL rp2040py-1.0.0b1-cp315-cp315-pyemscripten_2026_5_wasm32.whl
Size 6.3 MB
Tags CPython 3.15 PyEmscripten 2026.5+ WebAssembly
SHA-256 checksum
How to use checksums
deec2da588e2fe226043d3ef9c9b547873e9cc321d47907e4890965584b03ec4
BLAKE2b-256 checksum
How to use checksums
94a639f88281c8015753983d6ebb54006c19711767225f1babd27872d040a5b1
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315-android_24_x86_64.whl

Download URL rp2040py-1.0.0b1-cp315-cp315-android_24_x86_64.whl
Size 7.8 MB
Tags Android API level 24+ x86-64 CPython 3.15
SHA-256 checksum
How to use checksums
d151a3c1dcb20f77aaacfa132458c0f9fb6574a90d4d5ef3dde672862b7ef1ba
BLAKE2b-256 checksum
How to use checksums
c0e95a3570d789ef276462bc802dabccd6d6e4825dbd95cff775cdba2c6211ba
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp315-cp315-android_24_arm64_v8a.whl

Download URL rp2040py-1.0.0b1-cp315-cp315-android_24_arm64_v8a.whl
Size 7.7 MB
Tags Android API level 24+ ARM64 v8a CPython 3.15
SHA-256 checksum
How to use checksums
a84c135eb7cf4ba70b49bfdf3013270c4f177eb7703efebf3b481e9e238e2603
BLAKE2b-256 checksum
How to use checksums
ec6a50ee04e08ad26f10bd67197c83599055c1da57eb00f29c936ad5ce1bfd76
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-win_arm64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-win_arm64.whl
Size 7.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows ARM64
SHA-256 checksum
How to use checksums
2c9e9ec314575c8c9ce32890b5ee81d0b51cb1ddaadff83aaf36aa61a8e85219
BLAKE2b-256 checksum
How to use checksums
fa0104324839478cda5828246335996de29acdbd6899d23ed0d99fa7efd9678f
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-win_amd64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-win_amd64.whl
Size 7.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
723ea23e47eec8c830f3d352b89c727071693b9799f1a8fae8c0a0a85146f55f
BLAKE2b-256 checksum
How to use checksums
f632265caad026395edd0665683915e292ecd79942f49bd259de84f3cd4553fd
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-win32.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-win32.whl
Size 7.0 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-32
SHA-256 checksum
How to use checksums
24955d740c084f306ffc196b619f839e291866bc604d59b8dacd3e273a68ab46
BLAKE2b-256 checksum
How to use checksums
6572dd6d9a634921d692e4ccbec694791cce6562b9d11e01bc4b1968580ec892
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_x86_64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 8.7 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
8d9df09838bfda2e30b6653df2d6c5c57e003342442360aeb51602d2215a1849
BLAKE2b-256 checksum
How to use checksums
ead6e41b3d056646919358071f4678379f38b56eb1dbb1b6b610ea954896f48a
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_i686.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_i686.whl
Size 8.9 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-32
SHA-256 checksum
How to use checksums
e5a2ccbb139bc1ce174f3164cfb39aea214e7d3595c7bccc1e1c67bb0998252d
BLAKE2b-256 checksum
How to use checksums
c6d396eacad82f00f1a767d00ec76cba9287baaeabbf9bf0c89d888aebebb45e
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_armv7l.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_armv7l.whl
Size 8.1 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARMv7l
SHA-256 checksum
How to use checksums
d609e2cb86fda3aef9dac57065328369eee7c9969078cbc6cc80930a02bad270
BLAKE2b-256 checksum
How to use checksums
2e0f916cf4b6c38c6b476af1112bdfda39231128ecd7db5c10fc9006efe00844
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_aarch64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 8.5 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
9edca7513fe565355d5fefdab7afdf33f3a4542ac8b90be8ae77eef6405e6e10
BLAKE2b-256 checksum
How to use checksums
945eeffbc338ef8ff37d7f338deea3cef9a43a6e49b736cc793682144386d762
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-manylinux_2_26_i686.manylinux_2_28_i686.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 7.7 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.26+ x86-32 Linux glibc 2.28+ x86-32
SHA-256 checksum
How to use checksums
3f65967673a449c3c1bedf06ca135b21bbc95e791421dc818cb27a048e70e531
BLAKE2b-256 checksum
How to use checksums
3f2e1a04215ccaaf9cdd1a79bd8a716a79e2d32eb9fde9b4730eb52d7d3a9d63
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.6 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
12f8fae216c3615383a0d654fdc8a8cbf6d6ff0646c7b8ed232a9e2ac5a7c450
BLAKE2b-256 checksum
How to use checksums
ad362add70f9523ab3ee62413ec21029e3eae80c15f8a53a5be487eddd864cb2
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 7.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARMv7l Linux glibc 2.31+ ARMv7l
SHA-256 checksum
How to use checksums
2cbdb06b4e97c05b8a295f6ef9138129d2642903efdb3ea9bef38b223caf3319
BLAKE2b-256 checksum
How to use checksums
609d140ecba30a8b6414f92d6027a408a5848a842c3006aa7bc869fd566ae7e3
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 7.5 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
0921590de596b3e108a8e8cfa23ad7c9384ed09e36a9459c78af703613184642
BLAKE2b-256 checksum
How to use checksums
08be159d8faeaa5868b86757b21e90b91ce024551de32c1de706c6936298082f
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-macosx_11_0_arm64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-macosx_11_0_arm64.whl
Size 7.6 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
5156e17164788c82b3b2aba439a14b4886fd33ac0636cc6658ce4f0754a4bce0
BLAKE2b-256 checksum
How to use checksums
e6fece4d822df911942948ea1f19bb4416f478d29d4e562a6ae881c16b470ee1
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_x86_64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_x86_64.whl
Size 7.6 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
e2e76b24781d0235715d44440aedf39d1298a3233383cad6ce91f2c1c683d915
BLAKE2b-256 checksum
How to use checksums
18a076f84d79c9e66ea361e7279169bd0ee71af39e2b993f2319463b37d2b4a2
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_universal2.whl

Download URL rp2040py-1.0.0b1-cp314-cp314t-macosx_10_15_universal2.whl
Size 10.0 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 10.15+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
ffe0e0062f788c5d1486d6086d9f09ed91e6a79e56dc21b4306cc7192e5e4151
BLAKE2b-256 checksum
How to use checksums
ce0c4d3a934bd93bf9220faea062dafa6035c4882d478de2dca56385deccfd21
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314-pyemscripten_2026_0_wasm32.whl

Download URL rp2040py-1.0.0b1-cp314-cp314-pyemscripten_2026_0_wasm32.whl
Size 6.3 MB
Tags CPython 3.14 PyEmscripten 2026.0+ WebAssembly
SHA-256 checksum
How to use checksums
7f4c46732c7a5287ea8b7cd1b7fde0e16b7c37f6019b5721c285e4db85d2e423
BLAKE2b-256 checksum
How to use checksums
0fd9249033918395a4946efcc472b9995a7a6003520be24fe648f26aa9c3af0d
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314-android_24_x86_64.whl

Download URL rp2040py-1.0.0b1-cp314-cp314-android_24_x86_64.whl
Size 7.8 MB
Tags Android API level 24+ x86-64 CPython 3.14
SHA-256 checksum
How to use checksums
f72716031fe4464a4219eb72de75af4bbab6385ca7def55eff5495dfd15fb2b9
BLAKE2b-256 checksum
How to use checksums
935004a8afabd10368894ba4370126b517b8fc30f20fef4fe42dfe004cc7fa20
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp314-cp314-android_24_arm64_v8a.whl

Download URL rp2040py-1.0.0b1-cp314-cp314-android_24_arm64_v8a.whl
Size 7.7 MB
Tags Android API level 24+ ARM64 v8a CPython 3.14
SHA-256 checksum
How to use checksums
661acf65baee583ff83bb1a0edcd29899205290470517d2e4cfd0f8c2016a718
BLAKE2b-256 checksum
How to use checksums
1745b36d130d38ebb421e3f2690ef90ff0e51ef09f58a1bb21a282167a484406
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp313-cp313-pyemscripten_2025_0_wasm32.whl

Download URL rp2040py-1.0.0b1-cp313-cp313-pyemscripten_2025_0_wasm32.whl
Size 6.3 MB
Tags CPython 3.13 PyEmscripten 2025.0+ WebAssembly
SHA-256 checksum
How to use checksums
5ae6c4f9e1e9fdcd97ad829a3f19ca3e7e28875206e78b519c9e3e76bc8df97d
BLAKE2b-256 checksum
How to use checksums
117ed015bc316eb514ca7982794a78228c7a42bd5a6b062c8ab20b3168143dae
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp313-cp313-android_24_x86_64.whl

Download URL rp2040py-1.0.0b1-cp313-cp313-android_24_x86_64.whl
Size 7.8 MB
Tags Android API level 24+ x86-64 CPython 3.13
SHA-256 checksum
How to use checksums
20e1b3a132f5c0566c6f32d66013d10f934e82d19df6b416170cdbbf9f7fe6b0
BLAKE2b-256 checksum
How to use checksums
35ab1570fb86b7dc4ed70090e219700961f0d01b723c8a02d204e075f1c74100
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp313-cp313-android_24_arm64_v8a.whl

Download URL rp2040py-1.0.0b1-cp313-cp313-android_24_arm64_v8a.whl
Size 7.7 MB
Tags Android API level 24+ ARM64 v8a CPython 3.13
SHA-256 checksum
How to use checksums
3486359ecd5ed0abfd1909d713f8fd5c56daccd801fb4603b11631609768a87b
BLAKE2b-256 checksum
How to use checksums
0c2438412334702990fc16e0e7e74296c65276151550288eaae53a7a4ff6e016
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-win_arm64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-win_arm64.whl
Size 6.7 MB
Tags CPython 3.11 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
cc9b6d2ca5bc02ca54091e680ee242e39166fa42aec0dd416b1118bd1c920b96
BLAKE2b-256 checksum
How to use checksums
9503dcd7ef15e5878a411bbbf1f8ba22b0f7f37c3a29373aa839e10499b2f514
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-win_amd64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-win_amd64.whl
Size 7.0 MB
Tags CPython 3.11 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
f2070bac226b0638f0525128755dbb260bac49f9aee0d76da66e48ba1254a3f2
BLAKE2b-256 checksum
How to use checksums
b5a9be502bcd5d7488f2e84501ae3f73dfbd56847be7e2a25921a0571cb88307
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-win32.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-win32.whl
Size 6.7 MB
Tags CPython 3.11 Windows x86-32 abi3
SHA-256 checksum
How to use checksums
c5adeea997b2ccf301617007e0779e69c8558f0e8ff41a2a73556a68d4a5a6ea
BLAKE2b-256 checksum
How to use checksums
1c01ea46026d9eafe78398740492e81262160f8d643844c0f5b1614f34765dff
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_x86_64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_x86_64.whl
Size 8.5 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
8757963f56ff01b17d0b12aac3d273d2998696917736ae5529f09e7546656a81
BLAKE2b-256 checksum
How to use checksums
5b8c72cff81d24c45f3b87bf2f0e7196f588e9cccf02808922438d2238fa6a92
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_i686.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_i686.whl
Size 8.8 MB
Tags CPython 3.11 Linux musl 1.2+ x86-32 abi3
SHA-256 checksum
How to use checksums
f0eb505465843f3c62c221826315ebec89147248c3efbb66353c2de2ae481e20
BLAKE2b-256 checksum
How to use checksums
b0a941a3e380b5b2188af53de8638aa5f317a4e75cde61a71de7e7c17bcb360d
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_armv7l.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_armv7l.whl
Size 8.0 MB
Tags CPython 3.11 Linux musl 1.2+ ARMv7l abi3
SHA-256 checksum
How to use checksums
c262ca71157680701ea21e8e29c310eb94ac3b113c9febb47ffc8803739a9545
BLAKE2b-256 checksum
How to use checksums
b805050b31c5cac7dedd43651b9ef6712b1d35e34bba4d77bd4c55a594efb4e7
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_aarch64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-musllinux_1_2_aarch64.whl
Size 8.3 MB
Tags CPython 3.11 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
c7fd5aa41b5fdb5a56aff7688b56919c7883b47d96373acce51d59b5eb9185ae
BLAKE2b-256 checksum
How to use checksums
ade562ad955366984e36c1b85df325c97a2ca00a193e0c46dc2c66d9a99c4f22
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-manylinux_2_26_i686.manylinux_2_28_i686.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 7.6 MB
Tags CPython 3.11 Linux glibc 2.26+ x86-32 Linux glibc 2.28+ x86-32 abi3
SHA-256 checksum
How to use checksums
1c0ce6d67af0a8174caf9e3dabc736974ea3e63f9ce1f11d2acf8a8cc8984a0d
BLAKE2b-256 checksum
How to use checksums
fbaece9c112d9bbc2cd93d9d9e1bfd88a1ec95a33a2a29b09d5201947aa9208d
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.4 MB
Tags CPython 3.11 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64 abi3
SHA-256 checksum
How to use checksums
2242172772348daa8a5f351758eb03087d3c4b39d5f1e768f2299be91d4c4a15
BLAKE2b-256 checksum
How to use checksums
a4d9e489cc1115e15b759a1d15a486fa1869e7cc093b31ad3eea61d05e2ce63f
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 7.1 MB
Tags CPython 3.11 Linux glibc 2.17+ ARMv7l Linux glibc 2.31+ ARMv7l abi3
SHA-256 checksum
How to use checksums
64df92ceee5ee39d400fd8318af67e4815e9328b5449bfc9975c2d92ef98ab0b
BLAKE2b-256 checksum
How to use checksums
6659a6d94fbf9980b9858ab83364be91c5235dcde1564b6e7a69cc34443bfc68
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 7.3 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
6f9fda56b7177338a83633cb92a097321237c87dd266fa6851ded8dbf721e65d
BLAKE2b-256 checksum
How to use checksums
dd24952b48265fca2a55ffa4d1fca9ed51de2f79d4445c3ca9fd477a19abf37f
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-macosx_11_0_arm64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-macosx_11_0_arm64.whl
Size 7.2 MB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
581dd35864db8f3fb6ca69e9475a1d53380cdba382a76895d0ed79bc00ca6fc1
BLAKE2b-256 checksum
How to use checksums
6d93e532b9633a8abecba63775a5b9402372524d016455ac2cbe51562198a4c8
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_x86_64.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_x86_64.whl
Size 7.2 MB
Tags CPython 3.11 abi3 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
012c0b1b5ca61501392f684a9ece9ee93fb6129cca6aaa3b21de43141fd9def3
BLAKE2b-256 checksum
How to use checksums
dc4390a41958a031a04a63dd37b6453f85675a0f2abf8931ade02772ffcd78f7
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_universal2.whl

Download URL rp2040py-1.0.0b1-cp311-abi3-macosx_10_9_universal2.whl
Size 9.2 MB
Tags CPython 3.11 abi3 macOS 10.9+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
bcebb9569a0124e1c05cfc4a04386810a424d768a0db555dfde0f5289fba922c
BLAKE2b-256 checksum
How to use checksums
2ee20820a1bbf66de12bb4f7cb58273fa96df1aa2cffabe41e747f1e7d308be6
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-win_arm64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-win_arm64.whl
Size 6.8 MB
Tags CPython 3.10 Windows ARM64
SHA-256 checksum
How to use checksums
5632f7eb213dc5d0977a8781f70630a74e3ffe2e0ed7779d7602f21e0018ca69
BLAKE2b-256 checksum
How to use checksums
7759970107409688c64bbf8fe2b31bc2634ba896dc8ed8373766a74e218c6844
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-win_amd64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-win_amd64.whl
Size 7.0 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
e808481026091725c40718c187f69a68d6a624c972f2d4a8097299043f9b419e
BLAKE2b-256 checksum
How to use checksums
a3da137aca8c94932228fefadf4b0737003b788a10a0c2bde615c72618bb760f
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-win32.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-win32.whl
Size 6.8 MB
Tags CPython 3.10 Windows x86-32
SHA-256 checksum
How to use checksums
226f243f9803c1ef58ed584322828d25878bbc3353da07c5fceba257f4b20ace
BLAKE2b-256 checksum
How to use checksums
197e5f93f642d407af8bc89b0bcbe085e9b25504ac788ae98d0d0254835c3d36
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_x86_64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_x86_64.whl
Size 8.7 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
d9888cb61b7ba0f1460f134261ffbfd1944ccdf639f5b98652a34be7b6fef837
BLAKE2b-256 checksum
How to use checksums
ce8318955b27f19adfd88403e238291f0f03d3df35d6062c50770cc3607974da
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_i686.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_i686.whl
Size 9.0 MB
Tags CPython 3.10 Linux musl 1.2+ x86-32
SHA-256 checksum
How to use checksums
d0ce29554e21f5792abcc6aea66a91dcd41758577df8dd7bb7cd87238f33e841
BLAKE2b-256 checksum
How to use checksums
252a5116f8bfbb679d8859210dec07cc437ad0ecadafe4f11f7d9e100fe6973a
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_armv7l.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_armv7l.whl
Size 8.2 MB
Tags CPython 3.10 Linux musl 1.2+ ARMv7l
SHA-256 checksum
How to use checksums
41f300cd75c4d196ed2c0bf626d4bb98f0f13a6e9bd0bdf1dc84893810d82bb0
BLAKE2b-256 checksum
How to use checksums
ad315f828a42ab14d29d08780391d11fc856b0692f7015aa55b82402228a6893
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_aarch64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-musllinux_1_2_aarch64.whl
Size 8.5 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
94b80684cfdf176b15fd0a1999a3a306faceff830b3c3f20424d1a8ca434198d
BLAKE2b-256 checksum
How to use checksums
45198c1c82432e9e90d87187814059f1882b4b2add19f8b564cb71d4a2399cd2
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-manylinux_2_26_i686.manylinux_2_28_i686.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 7.8 MB
Tags CPython 3.10 Linux glibc 2.26+ x86-32 Linux glibc 2.28+ x86-32
SHA-256 checksum
How to use checksums
7ea75df2713dc8e514ddbbea55dcc1aaa10fa5aabecf6b7ef3285a4406488aa7
BLAKE2b-256 checksum
How to use checksums
f4547f10bfda50a0df21fc410e367fb84a64a4586378248f36ea23e724530340
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 7.7 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
06ae78d4afa59a5d32887fba0ef8ffa5395f85ffeb7f4a2bf8f786ec80a05ba2
BLAKE2b-256 checksum
How to use checksums
e4b45b212eb8799805fe3d37feec6a3332682f1aab15d520d40c7e798b70917d
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 7.3 MB
Tags CPython 3.10 Linux glibc 2.17+ ARMv7l Linux glibc 2.31+ ARMv7l
SHA-256 checksum
How to use checksums
4066b7064d20f2bcb9526504c61f2254146f5152dbd6cab1924ae720b9eae947
BLAKE2b-256 checksum
How to use checksums
b8fa575f756c2f82e2784c2f1b036a636438885949699343eb1ec90ec1046158
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 7.5 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
00abd08a9d30d04f71b8a4133066e2963b2b7e41d6ed6a9266cfabb0888e2b61
BLAKE2b-256 checksum
How to use checksums
9e46b5583e725173ec17cdde0e0b35875cfd726721c7cff07f72c297fdc04658
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-macosx_11_0_arm64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-macosx_11_0_arm64.whl
Size 7.5 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
7cf48eb4b81a9965ff835789b20cc3cd429eb1b36b01478fe643a37fa781ee53
BLAKE2b-256 checksum
How to use checksums
0ef8df2bb3a460742449190709c9435ee660dbbaa6958dcc7d97a716f29d350d
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_x86_64.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_x86_64.whl
Size 7.5 MB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
db04850915bc908c5460b050d3387015fea278b3cb7117bb5537b11c1583ed8d
BLAKE2b-256 checksum
How to use checksums
dc85ab3138891971deae29504e4420e003e4675d3a02f3db3a4b26a8ba0145a0
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 19, 2026.

Transparency log

Release files / rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_universal2.whl

Download URL rp2040py-1.0.0b1-cp310-cp310-macosx_10_9_universal2.whl
Size 9.8 MB
Tags CPython 3.10 macOS 10.9+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
83d3358c52414abf72a58c67d95bfaf6056a171387628f9dcecca075c52ee9ef
BLAKE2b-256 checksum
How to use checksums
8ce2b8fc0d10b3ece307bb2480383590ec40d495ba476ceeefca77b7e6123513
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 19, 2026.

Transparency log

Security for rp2040py 1.0.0b1

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 67 files in this release have been uploaded with provenance metadata.

Select from 67 files

Attestation for rp2040py-1.0.0b1.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 19, 2026.

Transparency log

A 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.

Release history Release notifications | RSS feed

This release
Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page