Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:    +0 +0.000% PYBV10
        rp2:    +0 +0.000% PICO

Nice work bringing it all together!

Alternate solution: https://github.com/pybricks/python-mpy-cross-multi (with binaries provided by https://github.com/pybricks/python-mpy-cross)

Advantages:

• Proper native Apple arm64 build
• Not limited to oldest GitHub CI Linux version
• Proper sdist that includes mpy-cross source code (but not full micropython source tree) so it can be built on platforms with no working binary wheel
• Having one mpy-cross-vX package for every MPY version allows a single application to target multiple MPY versions. This way, a single application can support both current and older MicroPython targets without having to have two versions of the application. (This seems useful for the micropython-lib "binary wheels" use case where we might want to publish mpy files for both the current stable MicroPython release and the development release which could have a different MPY version at the same time).
• The work is already done - happy to move the repository to the micropython organization and add MicroPython admins to existing PyPi projects.

Notes:

• Builds for 32-bit Raspberry Pi are available through piwheels.org rather than through PyPI.

Hi

Last year I open as issue regarding the usefulness of two mpy-cross utilities:
#11664

@jimmo Jim suggested to me to continue the discussion here.

I waited ... no hurry ... and now I ask for an update ;-)
Have the two versions been merged?

Docs

For the common man, IMHO, there must be a brief summary of this development in the MP's official documents.
And, if there were still two packages, it would be nice to have two lists of their respective pros/cons.

More recent related discussions:

• https://github.com/orgs/micropython/discussions/14394
• https://github.com/orgs/micropython/discussions/15176

@andrewleech was working on filling in some of the missing features in his version recently, so maybe close to no longer needing two different packages for different use cases?