QUERY · ISSUE
mpremote mip install can create a folder named `:`
bugtools
Port, board and/or hardware
ESP32 , but can be any
MicroPython version
mpremote v1.27.0
Reproduction
PS D:\mypython\mp_wcwidth> mpremote --version
mpremote 1.27.0
PS D:\mypython\mp_wcwidth> mpremote mip install --target : github:josverl/mp_wcwidth/demo.py
Install github:josverl/mp_wcwidth/demo.py
Downloading github:josverl/mp_wcwidth/demo.py to :
Installing: :/demo.py
Done
PS D:\mypython\mp_wcwidth> mpremote tree
tree :
:/
└── :
└── demo.py
Expected behaviour
Expected that :
- the : prefix for "remote" would not be used as the path
- the demo.py file would be created in the cwd of the MCU
- nu folder named
:would be created
Observed behaviour
PS D:\mypython\mp_wcwidth> mpremote tree
tree :
:/
└── :
└── demo.py
Additional Information
Similar issues with specifying '--target :.'
tree :
:/
├── :
│ └── demo.py
├── :.
│ └── demo.py
└── demo.py
Code of Conduct
Yes, I agree
CANDIDATE · PULL REQUEST
tools/mpremote: Add `mpremote mip install` to install packages.
tools
This supports the same package sources as the new mip tool. (https://github.com/micropython/micropython-lib/pull/542)
- micropython-lib (by name)
- http(s) & github packages with json description
- directly downloading a .py/.mpy file
The version is specified with an optional @version on the end of the package name.
Also adds support for optional --args to multi-arg commands like "edit" and the filesystem commands (and now "install"). This allows --mpy/--no-mpy and --target to be specified to the install command.
This work was funded through GitHub Sponsors.