How can I structure package.json to take advantage of --no-mpy option to mip?

[DavesCodeMusings]

I was today years old when I learned mpremote mip install can be used with an option of --no-mpy. But, I have no idea how I can update my package.json to take advantage of this option.

I'm assuming the idea behind --no-mpy is to prefer installing module.py over module.mpy when both module.py and module.mpy files exist.

My question is this... How can I set up my own package.json to make this work?

For example, I have a package.json for my sht3x module that looks like this:

{
    "urls": [
        ["sht3x.mpy", "github:DavesCodeMusings/SHT3x-MicroPython/sht3x.mpy"]
    ],
    "version": "0.2"
}

I'm assuming I can just add another file in the "urls" to reference the non-mpy version, like this.

{
    "urls": [
        ["sht3x.mpy", "github:DavesCodeMusings/SHT3x-MicroPython/sht3x.mpy"],
        ["sht3x.py", "github:DavesCodeMusings/SHT3x-MicroPython/src/sht3x.py"]

    ],
    "version": "0.2"
}

But, I'm guessing when running mpremote mip install, it will just install both files to the microcontroller's /lib directory. This isn't what I want..

How can I make it prefer installing the .mpy file unless --no-mpy is given as an option?

[Josverl]

TL;DR: You can't.

the --mpy/--no-mpy option is only valid when a package is installed from the MicroPython packet index
That has precompiled .mpy binaries for different bytecode versions, (AFAIK version 6 and up)

• --mpy uses 'https://micropython.org/pi/v2/package/6/upysh/latest.json' on a recent board.

• --mpy uses 'https://micropython.org/pi/v2/package/7/upysh/latest.json' on future boards .

• --no-mpy uses 'https://micropython.org/pi/v2/package/py/upysh/latest.json' on any board.

If you want to offer both .mpy and .py versions then :

• you can create two different package.jsons with different names / locations
• you could run your own package index, but that seems a bit much for one package.

See: https://github.com/micropython/micropython-lib/blob/68e0dfce0a8708e7d9aef4446fad842cc5929410/tools/build.py#L33-L112

[DavesCodeMusings]

Well, shoot! I was hoping it was just a matter of configuring something in the package.json. Thanks for the quick answer!

[Josverl]

I find that package.json and package-mpy-v6.json works quite well.
But agree it would be a nice feature if mpremote mip and mip would be able to match this on any repo.