uv tool + mpremote romfs gotcha

[Josverl]

Thanks to uv im now installing most tools using uv tool install <package>

While testing romfs I ran into errors : during mpremote romfs build folder/

'mpy_cross' module not found, .py files were not precompiled

As uv installs all tools into their own isolated venv, I would need to install it using :uv tool install --reinstall mpremote --with mpy-cross

uv tool install --reinstall .\tools\mpremote\ --with mpy-cross
      Built mpremote @ file:///C:/dev/micropython/tools/mpremote
Resolved 4 packages in 3.49s
Prepared 4 packages in 279ms
Uninstalled 3 packages in 178ms
Installed 4 packages in 396ms
 ~ mpremote==1.29.0rc0.post678+g5f2181f93.d20260810 (from file:///C:/dev/micropython/tools/mpremote)
 + mpy-cross==1.27.0.post2
 - platformdirs==4.9.6
 + platformdirs==4.11.2
 ~ pyserial==3.5 

That pulls in a (rather stale, but working @andrewleech ) mpy-cross, which then solves the issue

Would it make sense to clearly document this given the wide-spread use of uv ?
I assume that the same issue is when installing using pipx

[andrewleech]

mpy-cross should really be declared as a dependency in mpremote now it's used directly, that's cleaner than documenting a more complicated manual install.

Oh and yes thanks for the prompter, my mpy-cross auto-builder had stopped because the self-publish access token had expired. Rotating that key has been pretty much the only maintenance that project has needed for some years.

[Josverl]

a dependency would make it simpler , though the publishing order might be interesting

and commit 0c98c60 has been there for some ~4 years, so its about time I noticed ⏱️