Skip to main content

chumicro-timing

Timers that don't block. Your loop keeps ticking.

Capture ticks_ms() once per loop pass, hand it to a Rate or a Deadline, and you've got clean drift-free timing on CircuitPython, MicroPython, or CPython. Tick-source detection is automatic, wraparound is handled, and there are no dependencies on anything else in ChuMicro — it's where every other library starts.


Part of the ChuMicro family — small, focused Python libraries for microcontrollers and laptops. Browse all libraries.

Install

# CircuitPython (after `circup bundle-add ChuMicro/ChuMicro-Bundle`)
circup install chumicro_timing

# MicroPython
mpremote mip install github:ChuMicro/ChuMicro-Bundle/chumicro_timing

# CPython
pip install chumicro-timing

For bundle setup, pre-compiled .mpy bundles, the experimental channel, and details on PyPI naming, see the chumicro INSTALL guide.

Quick example

from chumicro_timing import Rate, ticks_ms

rate = Rate(1000, ticks_ms())

while True:
    now = ticks_ms()
    if rate.due(now):
        print("one second elapsed")
    # ... do other work ...

What's included

Tick functions

Symbol Description
ticks_ms() Current time in milliseconds — keeps counting even when it wraps around
ticks_diff(end, start) Time elapsed between two tick values (handles wraparound correctly)
ticks_add(ticks, delta) Add milliseconds to a tick value (handles wraparound correctly)

Value objects

Symbol Description
Deadline(period_ms, now_ms) A single armed timeout — expired(now) / remaining(now) / reset(now)
Rate(period_ms, now_ms) Drift-free periodic cadence; due(now) fires at most once per period

Wait vocabulary (chumicro_timing.waits)

Opt-in completion-wait vocabulary for generator flows — import explicitly.

Symbol Description
Signal() A completion flag — set(value) / clear() / ready(now)
wait_for(signal, deadline_ms=None) Generator suspension helper: yield from wait_for(signal)

Testing

Symbol Description
FakeTicks(start_ms=0) Deterministic tick source for host-side tests
FakeTicks.advance(amount_ms) Move the fake clock forward

Where this fits

Leaf — no upstream ChuMicro deps. Everything in ChuMicro that owns time depends on it: runner, sockets, ntp, requests, http_server, mqtt, websockets.

Platform support

You don't need to pick a tick source — the library picks the best one available on your runtime. Behavior is identical regardless of which source is used.

Source Runtime
supervisor.ticks_ms CircuitPython 7+
time.ticks_ms MicroPython, some CircuitPython builds
time.monotonic_ns CPython, some CircuitPython boards
time.monotonic Final fallback (float seconds → int ms)

The library tries them top-to-bottom and uses the first one your runtime supports.

Technical detail: tick wraparound

All sources are masked to a 2²⁹ ms period (~6.2 days). ticks_diff and ticks_add handle wraparound correctly, so your timers keep working even when the counter rolls over.

Testing your code

The chumicro_timing.testing module provides FakeTicks for deterministic host-side tests — no wall-clock waits:

from chumicro_timing import Rate
from chumicro_timing.testing import FakeTicks

fake = FakeTicks()
rate = Rate(100, fake.ticks_ms())

assert rate.due(fake.ticks_ms()) is False

fake.advance(100)
assert rate.due(fake.ticks_ms()) is True

Examples

Example What it shows
heartbeat_blink.py Basic periodic Rate loop
multiple_heartbeats.py Multiple Rate timers at different rates
timeout_check.py One-shot deadline check using ticks_diff
debounce.py Simulated button debounce
periodic_tick.py Manual periodic loop (the same logic Rate wraps internally)
phase_locked_tick.py Drift-free deadline carrier — same period across late loops
circuitpython_blink.py LED blink on CircuitPython hardware
circuitpython_debounce.py GPIO button debounce on CircuitPython
micropython_blink.py LED blink on MicroPython hardware
micropython_debounce.py GPIO button debounce on MicroPython

Contributing

Working on chumicro-timing itself? Clone the mono-repo if you haven't already — the rest of the workflow assumes you're inside that workspace.

pip install -e .[test]
pytest tests/                  # host-side tests
pytest functional_tests/       # on-device tests (needs a board registered in devices.yml)

Register a board before running functional tests: chumicro-workspace add-device <id> --address <port>.

Docs

📖 Stable docs · Experimental docs

Find this library

License

MIT

Metadata

Release files for chumicro-timing 0.8.1

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

Source distribution (sdist)

Source distribution for chumicro-timing 0.8.1
File Size Uploaded
chumicro_timing-0.8.1.tar.gz 22.0 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for chumicro-timing 0.8.1
File Interpreter ABI Platform
chumicro_timing-0.8.1-py3-none-any.whl Python 3 none any Details

Total release size: 30.5 kB

Release files / chumicro_timing-0.8.1.tar.gz

Download URL chumicro_timing-0.8.1.tar.gz
Size 22.0 kB
Tags Source
SHA-256 checksum
How to use checksums
46b7cc024eb93b4edfcf513ed1238399870be198b4ca80b785aa50410d45cac8
BLAKE2b-256 checksum
How to use checksums
27069471947134f8bbc01ad8db4227363015e22adf3078d8ebed8a7afa673574
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Jul 19, 2026.

Transparency log

Release files / chumicro_timing-0.8.1-py3-none-any.whl

Download URL chumicro_timing-0.8.1-py3-none-any.whl
Size 8.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0c0b0369fc190aaabb7d0babb98620363154279b6bd44901371a5958849eb220
BLAKE2b-256 checksum
How to use checksums
79701664b007a4502cf2fb1babe9b29647cfe3b7b7905b2355e00766746e6bec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.13

Provenance

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

PyPI Publish Attestation

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

Signed by GitHub Actions, verified by PyPI on Jul 19, 2026.

Transparency log

Release history Release notifications | RSS feed

0.8.4

2 release files

0.8.3

2 release files

0.8.2

2 release files

This release

0.8.1 This release

2 release files

0.1.25

2 release files

0.1.23

2 release files

0.1.21

2 release files

0.1.0

2 release files

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