The DSP repository was renamed audiodsp on 2026-09-21 and its distribution is pydevices-audiodsp from v0.5.0 (PyDevices/workspace#4). This build's python-for-android recipe still installs pydevices-audioif pinned at 0.0.4.
That keeps working — PyPI names are their own namespace, and the old one keeps its releases — so nothing is broken and nothing is urgent. But it is a build pinned to a core more than forty releases old.
What the move needs:
pydevices-audiodsp 0.5.x on TestPyPI, which p4a.extra_args already lists as an index (waits on the audiodsp release)- the recipe directory,
name, get_pip_name(), version and the requirements line in p4a_app/buildozer.spec changed together
- an APK build on at least one ABI behind it, because 0.5.0 is a different core from 0.0.4: it carries the pump engine and its port hooks, and nobody has cross-compiled that for Android
Until then tools/rename_gate.py in the workspace reports this repo as "still on the old PyPI package", which it counts as a to-do and not as a hazard.
The DSP repository was renamed
audiodspon 2026-09-21 and its distribution ispydevices-audiodspfrom v0.5.0 (PyDevices/workspace#4). This build's python-for-android recipe still installspydevices-audioifpinned at 0.0.4.That keeps working — PyPI names are their own namespace, and the old one keeps its releases — so nothing is broken and nothing is urgent. But it is a build pinned to a core more than forty releases old.
What the move needs:
pydevices-audiodsp0.5.x on TestPyPI, whichp4a.extra_argsalready lists as an index (waits on the audiodsp release)name,get_pip_name(),versionand therequirementsline inp4a_app/buildozer.specchanged togetherUntil then
tools/rename_gate.pyin the workspace reports this repo as "still on the old PyPI package", which it counts as a to-do and not as a hazard.