Skip to content

firmware modules: list modules pinned in DEPENDENCIES.lock - #223

Merged
bdbarnett merged 1 commit into
mainfrom
dependencies-lock
Nov 10, 2026
Merged

bdbarnett merged 1 commit into
mainfrom
dependencies-lock

Conversation

@bdbarnett

@bdbarnett bdbarnett commented Nov 10, 2026 •

Copy link
Copy Markdown
Collaborator

mpftp firmware modules lists the modules a micropython-pydevices checkout pins but hasn't fetched yet, marked "fetched on first build". It found them by calling build_mp.py's read_lock("modules.lock"). micropython-pydevices is moving its pins into one DEPENDENCIES.lock, read through a new lock() in build_mp.py, so the listing now uses lock() and its module lines when the checkout's build_mp.py has it, and read_lock("modules.lock") when it doesn't. Without this the listing wouldn't fail on the new checkout (the call was already in a try), it would just stop showing the unfetched modules.

The build-firmware guide's sentence about those modules no longer names the old file.

cli/tests/test_firmware_build.py passes, with a new case where the fake build_mp.py has lock() in place of read_lock(). Run against a checkout of micropython-pydevices' branch with the new file, with modules/ulab moved away, the listing shows audiodsp and pygraphics as present and ulab as not fetched yet, and no toolchain or MicroPython line as a module.

micropython-pydevices is moving its pins into one DEPENDENCIES.lock,
read through build_mp.py's lock(). The module listing takes the not yet
fetched modules from there when build_mp.py has it, and from modules.lock
otherwise.
@bdbarnett
bdbarnett merged commit 784d1f8 into main Nov 10, 2026
9 checks passed
@bdbarnett
bdbarnett deleted the dependencies-lock branch November 10, 2026 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant