the build failures seem to be unrelated to this PR and are failing on github internal errors while cloning git dependencies.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.38%. Comparing base (f1363d8) to head (01ce305).

@@           Coverage Diff           @@
##           master   #18712   +/-   ##
=======================================
  Coverage   98.38%   98.38%           
=======================================
  Files         171      171           
  Lines       22298    22298           
=======================================
  Hits        21937    21937           
  Misses        361      361           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Code size report:

Reference:  github: Install Python 3.11 for Windows CI runs. [f1363d8]
Comparison: tools/mpremote/tests: Add test for mip download command. [merge of 01ce305]
  mpy-cross:    +0 +0.000% 
   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
      esp32:    +0 +0.000% ESP32_GENERIC
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

I think this is a useful feature, Thanks for the contribution.

Would it be possible to add a test for this to the mpremote tests?
Even if the source is a local path (to avoid network issues) that would help ensure stability.

I'll review in more detail in the next few days.

@Josverl I've added a test. I'm still not sure whether running the python files with host python3 instead of running diff would've been better, so if you'd prefer that approach please tell me and I'll change the test.

upd: force pushed with rebase on top of latest master, fixed signoff.

Also I have been ponderign on the cmdline options.

to me the most obvious thing would be to use mip install for both local and remote install, and use the --path prefix (':') to differentiate where the module gets installed to, with the default being the MCU.

MCU default install:
mpremote mip install requests

MCU specific install:
mpremote mip install --target :/mylib requests

host local install:
mpremote mip install --no-mpy --target typings requests
or
mpremote mip install --no-mpy --target ./typings requests

I think the docs should clarify that --mpy, --no-mpy flags are only valid for the micropython index , or a warning should be given, when I request .mpy and the source only holds .py files.

for example :
mpremote mip download --mpy --target typings2 requests github:josverl/mp_wcwidth
will download partial .mpy , and partial .py

Also I have been ponderign on the cmdline options.

to me the most obvious thing would be to use mip install for both local and remote install, and use the --path prefix (':') to differentiate where the module gets installed to, with the default being the MCU.

MCU default install: mpremote mip install requests

MCU specific install: mpremote mip install --target :/mylib requests

host local install: mpremote mip install --no-mpy --target typings requests or mpremote mip install --no-mpy --target ./typings requests

I thought about it, but that would break backwards compatibility for the target, and it won't be obvious because it would just create the directories on local fs.

Then that is something to mention in the PRs
"Trade-offs and Alternatives" section