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 examples in the MicroPython CI script (run by the MicroPython CI workflow).

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 script, run by the Kaluma CI workflow, 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.0b2

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.0b2
File Size Uploaded Provenance Actions
rp2040py-1.0.0b2.tar.gz 2.5 MB With provenance Details for rp2040py-1.0.0b2.tar.gz

Built distributions (wheels)

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

Total release size: 451.0 MB

Release files / rp2040py-1.0.0b2.tar.gz

Download URL rp2040py-1.0.0b2.tar.gz
Size 2.5 MB
Tags Source
SHA-256 checksum
How to use checksums
f190c807d6c7e9ec2235baf08ceed769c13a6279d9c2aa1afd194bc6399329fb
BLAKE2b-256 checksum
How to use checksums
d2c8d1bbb1ed8f27f74c65d53a30644575c6572d55b7e3d2224f729e906cb77f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-py3-none-any.whl
Size 860.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
8c45b94223936d12e2e7fd2ed1df42f4fcf59e9e123e5ebffac975aa8a072360
BLAKE2b-256 checksum
How to use checksums
1bf1a5a5eafc35bf0bd9dedb4d6f007cfa0d0db44cad7c460ee1a5c8347fa5bc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-win_arm64.whl
Size 6.2 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows ARM64
SHA-256 checksum
How to use checksums
49ebaa84610b22cb4f1856a0116b7a2f7811bfca80c5fd9325c8c39b583dd7d3
BLAKE2b-256 checksum
How to use checksums
ea854e86c324c9c3ddfa190504801f19b8298589252b446ec526be59dfb9cfba
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-win_amd64.whl
Size 6.4 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
74138d8a844ca16bdb2f6165db834461d3ac193a924138863be080200554280b
BLAKE2b-256 checksum
How to use checksums
8266a82e71514fca4d3258fbd3c5824b2ac5054dee6ebf589132c6334c24d955
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-win32.whl
Size 6.2 MB
Tags CPython 3.15 CPython 3.15 free-threading Windows x86-32
SHA-256 checksum
How to use checksums
38278a00716c5d1c7f378f394b27a3cf242123b73b90923311b3a0dc6b165ac7
BLAKE2b-256 checksum
How to use checksums
91638d70025326c6aaf8f0852ab6e0534d72e6dbb81a5799e0af763b01095947
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-musllinux_1_2_x86_64.whl
Size 7.8 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
93f71fae7e0af46e52296e9ecae8b41a3edd7a17eb693dded48ab386dddea30d
BLAKE2b-256 checksum
How to use checksums
b4e6f7fcb7ab4298abfaa8e996e3d86352e00160e14bde3716ad98463c6ba3c1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-musllinux_1_2_i686.whl
Size 7.9 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ x86-32
SHA-256 checksum
How to use checksums
4022b748331cdb1adc3ed9d3559511851e8bc7a8a512a68e115909629612d159
BLAKE2b-256 checksum
How to use checksums
2bdaeb054e789e1c2cad67177b18dada6faa9b59880b7cce3d2c5c51c5c85655
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-musllinux_1_2_armv7l.whl
Size 7.4 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARMv7l
SHA-256 checksum
How to use checksums
4003de02c2647211170534fe4db8cb9d8d1a18a22dfd43c8a3d7a6775abfb775
BLAKE2b-256 checksum
How to use checksums
4e7f0224b9f6ca8782f14f7c76aceb7d64215218a3d50532f23361573ef1cdff
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-musllinux_1_2_aarch64.whl
Size 7.7 MB
Tags CPython 3.15 CPython 3.15 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
22af6ca19e3f33672b2f97d801e7ab52077a0503319cf16cdaf3dc13fa190a90
BLAKE2b-256 checksum
How to use checksums
7997e813124e19b2f6e5c25682b5f9672a932682736e0cf2286c89593a97c567
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 6.7 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
04aa182118d130ed203f1b0cab3efbd5f552335adbf18e96e7dba9d0ee17776f
BLAKE2b-256 checksum
How to use checksums
293b33823c0956209952f3c08c1f0b6a4c6944071979670a4e433a3035182057
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 6.7 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
c844851e7a06e1c1ad8d521d605eed7928fac30cb731059295fdb0c20d9cdfd6
BLAKE2b-256 checksum
How to use checksums
7270a33c57d71a8d46074eda121fd7f22b4476249520f3d42a50befdc1d738a7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 6.6 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
3d0b749dc6643a6ceb5f87f99be6330b917198f52543f468e00b60bc00e4e95d
BLAKE2b-256 checksum
How to use checksums
4ec20fe7dc239ae7b64474044ee81aee73985c0ad8699a3c14cc26d02b220cc6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 6.7 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
6984b710c64678f8d5c967202205c057952b37bab7a1bfa79b91f9067efe7eb4
BLAKE2b-256 checksum
How to use checksums
9830bc04a349e2f586fab738285233843e9e531a49a4936d88823dd230185a85
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-macosx_11_0_arm64.whl
Size 6.6 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
796865602b44c86cb3c29efd3d8c72fef9661b2ac0ee6b32f24a53f43c111b4b
BLAKE2b-256 checksum
How to use checksums
45670b4519d9e8a6220e5400baf5bedd8a3c78739ddf65ff85faf92804b4a840
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-macosx_10_15_x86_64.whl
Size 6.6 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
678c0dc8752a9147fe20579b1e76ae72f5b8f268324184ff7725d7087572f5b7
BLAKE2b-256 checksum
How to use checksums
8401ed5901ab7e773c52d2c29f062843a511dc8336569c14315c3622c156d49a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315t-macosx_10_15_universal2.whl
Size 8.6 MB
Tags CPython 3.15 CPython 3.15 free-threading macOS 10.15+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
d39e32eaf030c8a44b9c76be24e0c25fbdfa3135f7130194805098b8b12247eb
BLAKE2b-256 checksum
How to use checksums
13c86834d20518a60e36dfbea0525a1171e949894bade17edd271f49f027ec38
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315-pyemscripten_2026_5_wasm32.whl
Size 5.6 MB
Tags CPython 3.15 PyEmscripten 2026.5+ WebAssembly
SHA-256 checksum
How to use checksums
39cabc967fc7fd37995e0d71df7920011146676f11a4dbae63e16754e0845758
BLAKE2b-256 checksum
How to use checksums
f067f150e43082996795c0a9584c2cfbd2166fa973b2b03f49d46dd7722d0e11
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315-android_24_x86_64.whl
Size 6.9 MB
Tags Android API level 24+ x86-64 CPython 3.15
SHA-256 checksum
How to use checksums
48e111ebfdef2c92c1c5adcc02a6075d40d7d55911ce02739325e93ed6df229c
BLAKE2b-256 checksum
How to use checksums
51219162c9624af12999d99414c13f3555c3661e60df38dda9c2963c174faaaa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp315-cp315-android_24_arm64_v8a.whl
Size 6.8 MB
Tags Android API level 24+ ARM64 v8a CPython 3.15
SHA-256 checksum
How to use checksums
48956c57a5fe73e0e35301871a24d0819ff5c61fae656b88537adc1705a63788
BLAKE2b-256 checksum
How to use checksums
be6d804ad0e4312bb1214208879e53aaf0c9652bb08546b48190dfc955c2c673
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-win_arm64.whl
Size 6.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows ARM64
SHA-256 checksum
How to use checksums
82d0f55dd4ad911fb529c01c7b38cd83aa2e9d1056ff450d5dc927a88d2d4b87
BLAKE2b-256 checksum
How to use checksums
2c97833cc1b080c574d670103f647c7ab300858569d1ce9520122b0dc4fb55e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-win_amd64.whl
Size 6.4 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-64
SHA-256 checksum
How to use checksums
ee3583d5f8995377cb3ca17c76fe9baadf660a36891eecdbfc663c4e364acb35
BLAKE2b-256 checksum
How to use checksums
b286aaf511966e2b2cf77bca31cdc341a1e751b79ee7e480d42cc835fd03366f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-win32.whl
Size 6.2 MB
Tags CPython 3.14 CPython 3.14 free-threading Windows x86-32
SHA-256 checksum
How to use checksums
a61006861dccb4114ac079d2e5ef46fb88bc0312d84270a9ce2bcc31f7be14c9
BLAKE2b-256 checksum
How to use checksums
9be64af72dfd410ccde182a0a2e65ca7852f6d2fd072fe09556973af3e296063
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-musllinux_1_2_x86_64.whl
Size 7.8 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
3fd7d6861df9f3455f24a2db5ed4f07b2e2e21bfe5b1df42eed09c0cbdc9a277
BLAKE2b-256 checksum
How to use checksums
8b88f310ed431635ed9911362b22a62ed450ec8bbc096be123257d0aa2e56cd5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-musllinux_1_2_i686.whl
Size 8.1 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ x86-32
SHA-256 checksum
How to use checksums
abd04c074807a1372a931b7892b14e342e426734dbaf22c69b9fd861a3c020e8
BLAKE2b-256 checksum
How to use checksums
4365a3a79613d8037147b56dc1201f917f586be9f7077f1958cdd1f9d0cbb9d6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-musllinux_1_2_armv7l.whl
Size 7.3 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARMv7l
SHA-256 checksum
How to use checksums
71c342581e2ae044f54d9090c3be05cf6e28c3c260e1def762a6654255f3aee2
BLAKE2b-256 checksum
How to use checksums
763e02ce8641511815c4e4a7af1ca0904411275530de9483f27e0a5d5966411c
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-musllinux_1_2_aarch64.whl
Size 7.7 MB
Tags CPython 3.14 CPython 3.14 free-threading Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
6684faaeb93ef647c4fd08f68dca1a341b07216e7de6705a793fcf967d01f486
BLAKE2b-256 checksum
How to use checksums
608eb39daf552106caec901a939e94353896ce1df85f2f927b089b1e2f82def8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 6.9 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
5e3df6e80bf29014817e3f8c271dd1516c8cc93cef9e6a6bb73dc4d3cca9545d
BLAKE2b-256 checksum
How to use checksums
3ddd7ecc668e91157bf39ac04ef1a8d947a7c1bb666ac111b165f2969afb665d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 6.7 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
078e92c66db61dcbcb67c2a074c842a45f85e8ac5d4413f57677beae9b0b9cae
BLAKE2b-256 checksum
How to use checksums
3db2f2fd1eb1119591f304f4ba75dd01b85d15fb7df65e54d7aeb5d60dcc4f86
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 6.4 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
cc22217e2883d49381827a1dd5a8ec426a8b43a3ff3e8cbf5fa9a141ec0377c6
BLAKE2b-256 checksum
How to use checksums
a1f7e25beeec15faa7db68964de692288a72e224d388b637e1d7e50ac7a06ef8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 6.7 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
c05246717d150ebb795588ee17d864c53e0d68f24e703e4f29fcd25f0b4ca763
BLAKE2b-256 checksum
How to use checksums
d02ce7e05449667dd2f0f99c60a1eec551dbe6827219b8786213c30d7aee2db5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-macosx_11_0_arm64.whl
Size 6.6 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
6ec41d3ebb1f701108be3c31491672b15d8b168842d5c64cdfe6f3d8cad6fae4
BLAKE2b-256 checksum
How to use checksums
58a8080c340b3fd99773a56bd604a09586e77d4ffce634224f835a6e0cf1e4e5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-macosx_10_15_x86_64.whl
Size 6.6 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 10.15+ x86-64
SHA-256 checksum
How to use checksums
bc18a9b95ccd5289702073142840ae9a6c06e7fa7530e7580e4d06c975810cf7
BLAKE2b-256 checksum
How to use checksums
516b6469a2f4fdaf402d9f1dcbebe6a1fbc67b4e9110907f003b4589fc287be8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314t-macosx_10_15_universal2.whl
Size 8.6 MB
Tags CPython 3.14 CPython 3.14 free-threading macOS 10.15+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
6cdf78601e5833348e36941919f20082f0d6145b014cec86cdc029c19c2b5c30
BLAKE2b-256 checksum
How to use checksums
562e8f7d44eb50d41704019fb3792d93079495aa24271eb48898ee2ed0a3b980
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314-pyemscripten_2026_0_wasm32.whl
Size 5.6 MB
Tags CPython 3.14 PyEmscripten 2026.0+ WebAssembly
SHA-256 checksum
How to use checksums
cc7737bf3105fadfc547f1b7ea2879da44e27f5b0a6269e31ef011f639408243
BLAKE2b-256 checksum
How to use checksums
9ca1ca2826a1ee33d4f05ea46ad040af5c1126b9898444de64213aa6464dc0df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314-android_24_x86_64.whl
Size 6.9 MB
Tags Android API level 24+ x86-64 CPython 3.14
SHA-256 checksum
How to use checksums
b08a42563de459cf2471036165b873492baaa5e354a40d93e783a96304f9fa7d
BLAKE2b-256 checksum
How to use checksums
aec680d8a5cbee9995bc786c8c0f2df19b8fb690e2bf86023f0d5e5afb60db7e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp314-cp314-android_24_arm64_v8a.whl
Size 6.8 MB
Tags Android API level 24+ ARM64 v8a CPython 3.14
SHA-256 checksum
How to use checksums
b0562977259c405d0c05dbdb6cf572d5f6a312e95c744b333f23f75dbb0dc49d
BLAKE2b-256 checksum
How to use checksums
8cebcfb99198b6d35c7642c6716b9dcbaaec44eaebeaa4a1b484f805c36ac5ab
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp313-cp313-pyemscripten_2025_0_wasm32.whl
Size 5.6 MB
Tags CPython 3.13 PyEmscripten 2025.0+ WebAssembly
SHA-256 checksum
How to use checksums
7246f2634257953cecb9258ab58afc4db3d56b0a9baca6bf95a208bf3ef264a6
BLAKE2b-256 checksum
How to use checksums
65e295265653567c62c9c07decff6ef61e725b4d44a09aa51e6b6dfb3f148f36
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp313-cp313-android_24_x86_64.whl
Size 6.9 MB
Tags Android API level 24+ x86-64 CPython 3.13
SHA-256 checksum
How to use checksums
e94ac32eb25b91346c7ae260d1122336e07251b8bb8daa2ebe70c159829aba8c
BLAKE2b-256 checksum
How to use checksums
3d321221302db57e97822ef9c095d273c242e4dc5b3ea60d53a433a00d6467f4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp313-cp313-android_24_arm64_v8a.whl
Size 6.8 MB
Tags Android API level 24+ ARM64 v8a CPython 3.13
SHA-256 checksum
How to use checksums
d5e3c0fb2bc0c6c7e647503795f07be5b0192392330557e8597c31bd1aa54c77
BLAKE2b-256 checksum
How to use checksums
29cb6a998da90afb1cc0923b8e10d4ab15eee898c5f1fa153a430240106679df
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-win_arm64.whl
Size 6.0 MB
Tags CPython 3.11 Windows ARM64 abi3
SHA-256 checksum
How to use checksums
633b9a2afbbfca540839d7e8cd36aa788095d80e6068885a51e180776fc60b32
BLAKE2b-256 checksum
How to use checksums
0952103005d435a61d1e268e42284d96cd50c788d51b44f790565e5892e6ff32
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-win_amd64.whl
Size 6.2 MB
Tags CPython 3.11 Windows x86-64 abi3
SHA-256 checksum
How to use checksums
879462dba532387308067ae9990540cc52743550c50012f2446a6e7ade9b3eb0
BLAKE2b-256 checksum
How to use checksums
c7a6d88e76cdd032cb2bd551161954223766f7717538cdac0b7a8d489cc5605a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-win32.whl
Size 6.0 MB
Tags CPython 3.11 Windows x86-32 abi3
SHA-256 checksum
How to use checksums
6ef7edc0c8812b6743860313f75e36d2b0c21277d8218c5002672c56fee99d38
BLAKE2b-256 checksum
How to use checksums
e22f8aeae0fd7a7f5f805fe587b1d648296e4b6722090197a9298f7d66e77f67
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-musllinux_1_2_x86_64.whl
Size 7.7 MB
Tags CPython 3.11 Linux musl 1.2+ x86-64 abi3
SHA-256 checksum
How to use checksums
f5e12f2c7ce384ebd25911e8f2b14651e758d43c77507f41d78d946467598808
BLAKE2b-256 checksum
How to use checksums
b431899c3bea88044d5311615ebd4677be817a989973b29b77898a2e1caf18fd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-musllinux_1_2_i686.whl
Size 8.0 MB
Tags CPython 3.11 Linux musl 1.2+ x86-32 abi3
SHA-256 checksum
How to use checksums
2bf815d235123ce087c52b7ce44bfe6c56e803777c77e7127249cb2ae2cd4b8a
BLAKE2b-256 checksum
How to use checksums
aee7730dc48dacd2f1ff51bb997a04c6563d310556f882da49e49a2a7f827d64
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-musllinux_1_2_armv7l.whl
Size 7.2 MB
Tags CPython 3.11 Linux musl 1.2+ ARMv7l abi3
SHA-256 checksum
How to use checksums
247447133e1d372649c75eff8ba9e9f99e8c0a1bdcc673f7357db876b3c5526f
BLAKE2b-256 checksum
How to use checksums
89fa709361e7ce38e1cc99f37904fa5d1695a6facbcd75bb95ba3c0ec72d48e1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-musllinux_1_2_aarch64.whl
Size 7.5 MB
Tags CPython 3.11 Linux musl 1.2+ ARM64 abi3
SHA-256 checksum
How to use checksums
7b1b70f75fa1377ae551a88593f2a0549bf7643127fb90f181bc3ee9524112e4
BLAKE2b-256 checksum
How to use checksums
9e4cf9e841e9545123318669e06fd05571f8fe252eaf230b27464948c8d27dfd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 6.9 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
c8c718434c8cbb03aae4411d3fd5fab16538fc1f7e284bc6b1732f027107b533
BLAKE2b-256 checksum
How to use checksums
13747bd9ff94b5bdbf1f77b3e512bad1e347acc6d4746d646eea5cfe8c357abf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 6.6 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
5b54b6d64956b4d4d94d4f7d2cd7ef2b196d1badb70287fb980941196c8689fb
BLAKE2b-256 checksum
How to use checksums
70ac879ef2e9d11171f101cda2a9da224687744f605541db743ca04695b1789d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 6.4 MB
Tags CPython 3.11 Linux glibc 2.17+ ARMv7l Linux glibc 2.31+ ARMv7l abi3
SHA-256 checksum
How to use checksums
731fb431bdad33016a082b19f614e448b2706a8da3d6af254f0a63b392c200ed
BLAKE2b-256 checksum
How to use checksums
129f605e20a003f7e6faadb4efd15b28a89852b2bb300d83ebb1e28ddfb48e68
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 6.6 MB
Tags CPython 3.11 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64 abi3
SHA-256 checksum
How to use checksums
f30251c3005052fccbcc4fadcd7ed57e220845a57c316f1bda67fd2e70cd9b9b
BLAKE2b-256 checksum
How to use checksums
19803e819a8a56aa82c866c508b0036723398351eb1ce7433e38d91816037f30
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-macosx_11_0_arm64.whl
Size 6.4 MB
Tags CPython 3.11 abi3 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
817d78c2fac00fd937e8e752790f29d1652ffd89d02dbd610a084664a25ae3cc
BLAKE2b-256 checksum
How to use checksums
5cc4be3511c1b1a8bfc5b183a91a542025744d92b648aee475df9b1585ff9e6f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-macosx_10_9_x86_64.whl
Size 6.3 MB
Tags CPython 3.11 abi3 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
87c85d1f9ae4f62362ec69bbca728055705729403ecdea42a8679a2f92530286
BLAKE2b-256 checksum
How to use checksums
c13ccc3edd7893ab3f8f1ed59489c4d09ca462d4ed7a1f2b5946ac9fc54deee4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp311-abi3-macosx_10_9_universal2.whl
Size 8.1 MB
Tags CPython 3.11 abi3 macOS 10.9+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
547f57131d7ba8f72b41c54b29e2373688020ad888f84403df8750eaff30d969
BLAKE2b-256 checksum
How to use checksums
c8100ab0baa97596214570224ecd12207714161d4de4244e1195085b454888a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-win_arm64.whl
Size 6.1 MB
Tags CPython 3.10 Windows ARM64
SHA-256 checksum
How to use checksums
c4bb74d0a4d29c7c923bc0afa64264295ae4a43727eb90c38f72ed0cd6d96add
BLAKE2b-256 checksum
How to use checksums
08ff0e1d647afa970114142af3bc2e563be156e331181bd225e179fffc094491
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-win_amd64.whl
Size 6.2 MB
Tags CPython 3.10 Windows x86-64
SHA-256 checksum
How to use checksums
90852f18a6d84827685e461e109965ff26a91dc3a92642db56248bbb72fe0f81
BLAKE2b-256 checksum
How to use checksums
7a0d92ce3c73ca6f6828ec00c2016e7a01c44aa4bd5af76cc581e2db0db4cb02
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-win32.whl
Size 6.0 MB
Tags CPython 3.10 Windows x86-32
SHA-256 checksum
How to use checksums
ac8294ddb82898c530a13d78f825e90de62409a2b5eb3681cdced5dee7b18285
BLAKE2b-256 checksum
How to use checksums
771b0429ac5b9af02a5cbc0cbcb2c0dbd2ba82b84ef1f1f9fe6d5bbe584dc737
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-musllinux_1_2_x86_64.whl
Size 7.8 MB
Tags CPython 3.10 Linux musl 1.2+ x86-64
SHA-256 checksum
How to use checksums
5bc253472fda3c09151096f1907cb172257a8df9024d6797cb1a16014b889c27
BLAKE2b-256 checksum
How to use checksums
6a134d704ca11b208e66a28d03a65cc374f766094049558052dda1fb95b7ee51
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-musllinux_1_2_i686.whl
Size 8.1 MB
Tags CPython 3.10 Linux musl 1.2+ x86-32
SHA-256 checksum
How to use checksums
1c1e47640c7327b77559186fe18b3b0944f5a2b5c7077a6465b2d958bdc15517
BLAKE2b-256 checksum
How to use checksums
a91d497ab279c465120e912b9fa07e0dd6836fad4749a9784048fbfdebe3f1a9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-musllinux_1_2_armv7l.whl
Size 7.3 MB
Tags CPython 3.10 Linux musl 1.2+ ARMv7l
SHA-256 checksum
How to use checksums
5d3382fe62d614952b24ae78f198247e8b3915b626b2eb121fac20a6d99c1ee3
BLAKE2b-256 checksum
How to use checksums
64fbd8a5dcc623df438670fb95d9ea4055a6706a43f51e49c64c66dae484f497
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-musllinux_1_2_aarch64.whl
Size 7.7 MB
Tags CPython 3.10 Linux musl 1.2+ ARM64
SHA-256 checksum
How to use checksums
694bc0b0bd0926cae6f907ac7c2a7a5975fe9cb284298050084e04c3f3aa3079
BLAKE2b-256 checksum
How to use checksums
be3fe9cc6d1e0eff7e0d41ec0551ee5288f8c0e9930399d2e7c7819753d444a1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-manylinux_2_26_i686.manylinux_2_28_i686.whl
Size 7.0 MB
Tags CPython 3.10 Linux glibc 2.26+ x86-32 Linux glibc 2.28+ x86-32
SHA-256 checksum
How to use checksums
6cd529695ee16cfd547dc1df09e82463e80a671086329d99e5c5e9008d48e260
BLAKE2b-256 checksum
How to use checksums
8dde5666f02e6917790ae3a60f15ab35c8309dc64aa8e93dac40b9904546e6bf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-manylinux2014_x86_64.manylinux_2_17_x86_64.manylinux_2_28_x86_64.whl
Size 6.8 MB
Tags CPython 3.10 Linux glibc 2.17+ x86-64 Linux glibc 2.28+ x86-64
SHA-256 checksum
How to use checksums
cf9ac342f8860ca52e83451d13e3b17ed08ca2a2484f53ba499b54d745d5a13f
BLAKE2b-256 checksum
How to use checksums
d9b61df11c91340772ce49f358dc9b5ec6e8f0617150f4b19d0356b9e2b48437
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-manylinux2014_armv7l.manylinux_2_17_armv7l.manylinux_2_31_armv7l.whl
Size 6.5 MB
Tags CPython 3.10 Linux glibc 2.17+ ARMv7l Linux glibc 2.31+ ARMv7l
SHA-256 checksum
How to use checksums
3f20587bd1a5d8f5641937048b5c55a2b027a473568eef5744db8a2d0051cb7e
BLAKE2b-256 checksum
How to use checksums
e3e3275de3cdc0d3b2ccb2df8f985e944bf3b182c8a193e7884af591f165c3de
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-manylinux2014_aarch64.manylinux_2_17_aarch64.manylinux_2_28_aarch64.whl
Size 6.7 MB
Tags CPython 3.10 Linux glibc 2.17+ ARM64 Linux glibc 2.28+ ARM64
SHA-256 checksum
How to use checksums
311da640c9762119721ae9eb229ffa18f91c1855e91fcee89a78b7dcf5c38e57
BLAKE2b-256 checksum
How to use checksums
7c52aaad74d275570c3b20087d8269820205fbd08d7e346d96a32f1fd0b790fc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-macosx_11_0_arm64.whl
Size 6.5 MB
Tags CPython 3.10 macOS 11.0+ ARM64
SHA-256 checksum
How to use checksums
6e66b4d410b8c7d30b028bd22473f32178598c6b27ce71e9af7d7e6b72072956
BLAKE2b-256 checksum
How to use checksums
f12d583117c04e05ea65d325028a6fb8f1a43c1d629302774736f1e62e07c4dc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-macosx_10_9_x86_64.whl
Size 6.5 MB
Tags CPython 3.10 macOS 10.9+ x86-64
SHA-256 checksum
How to use checksums
01324c791681c7efd8d7f14845d5d87c07235858791056155417bd40a231fc75
BLAKE2b-256 checksum
How to use checksums
c6da5d1215b856d3a9b6c57f6ce8edc3248861b491fa64a538e36100c48a21e9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

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

Download URL rp2040py-1.0.0b2-cp310-cp310-macosx_10_9_universal2.whl
Size 8.4 MB
Tags CPython 3.10 macOS 10.9+ universal2 (ARM64, x86-64)
SHA-256 checksum
How to use checksums
b14ed89d2165a4f79c3421b0baad5fc87d2504344a78bdd65c052aaf7235656f
BLAKE2b-256 checksum
How to use checksums
a15e3419837dab879032e74816be11df84ad39b4a936586bb1d5ded5f87aca82
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Security for rp2040py 1.0.0b2

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.0b2.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 27, 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