Skip to content

MIP sync runs publishing-v11, which predates own-package: bledev ships inside pydevices #56

Description

@bdbarnett

pydevices' mip-split.toml marks [bledev] as own-package = true with requires = ["aioble"], so a board without a radio shouldn't carry BLE. On the live index it doesn't work that way. package/6/pydevices/latest.json for 0.6.1 lists 14 bledev/*.mpy files inside pydevices, and there's no standalone bledev package (package/6/bledev/latest.json is a 404). A board install of pydevices 0.6.1 on the T-Embed confirmed it: 44 of 44 files matched that manifest, bledev included.

Why: PyDevices/mip calls reusable-synchronize-mip-package.yml@publishing-v11. v11 (ee7538a) predates 2842ca1 "pydevices publishing: own-package MIP packages and PyPI extras", which is on main only. git show publishing-v11:scripts/synchronize_mip_package.py has no own-package handling at all. The PyPI extras from the same commit are presumably missing from the pydevices wheel build for the same reason.

What to do: cut the next publishing tag with the documented tag script, move the callers to it, then check with the next pydevices release that the index shows a standalone bledev package (with aioble included) and a pydevices package without bledev/.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions