RFI: MicroPython port vs default micro:bit Python vs MakeCode Python

[MarcelHeemskerk]

To my understanding there are three types of Python for the micro:bit

• MakeCode Python (makecode.microbit.org) based on the MakeCode blocks

• "default" MicroPython (python.microbit.org)

• Official MicroPython Port (https://github.com/microbit-foundation/micropython-microbit-v2/releases)

Can somebody explain the differences? Is it pre-compiled vs interpreted? Do the two MicroPython ports have the same functionality? How about REPL and Raw REPL support? Can we have a feature and compatibility comparison table?

Thanks 🙏

[martinwork]

There is no default micropython in micro:bit

The hex files in the releases folder, compiled from this repo, contain "firmware" from the point of view of a python program, providing micro:bit micropython runtime, interpreter, REPL, and storage for python program text and other files.

The Python Editor (python.microbit.org) uses this firmware. It sends micro:bit both firmware and python text, or just the python text, if the firmware is already present. It saves hex files with the python program text embedded in the firmware - actually with separate firmware + program sections for V1 and V2.
https://tech.microbit.org/software/spec-universal-hex/

The micro:bit micropython firmware runs on micro:bit's target MCU, just like a MakeCode program, as opposed the micro:bit firmware, which is a program for the USB interface MCU.
https://microbit.org/get-started/user-guide/firmware/
https://tech.microbit.org/software/daplink-interface/

MakeCode compiles it's programs. This article looks at the differences.
https://support.microbit.org/en/support/solutions/articles/19000111744-makecode-python-and-micropython