QUERY · ISSUE

MicroPython compatability issue with CPython

openby redradistopened 2020-06-15updated 2024-08-28

docs

Hi all,

I am wondering why MicroPython have so many inconsistencies with standard CPython ?

Do you plan to make it fully compatible with CPython ?

We need it because it split ecosystem and decrease compatible between libraries for MicroPython and CPython

CANDIDATE · ISSUE

Why MicroPython isn't tailored from CPython

closedby yang8621opened 2020-07-20updated 2020-07-21

Hi,

Just noticed MicroPython, which is very helpful for embedded systems.
Just for my curiosity, why create micropython from zero and then to keep compatibility with CPython?

Why not tailor CPython to "MicroPython" as a minimal set?

Thanks.

Assessment

S Sonnet · medium

Both are open-ended philosophical questions about MicroPython's relationship to CPython, filed against the issue tracker rather than as bugs or feature requests. Issue 6154 asks why there are inconsistencies and whether full CPython compatibility is planned. Issue 6261 asks why MicroPython wasn't derived from CPython instead of being written from scratch. The framing differs (compatibility gaps vs. implementation origin), but both reduce to the same root question: why does MicroPython diverge from CPython? Any answer to one would substantially address the other. Neither contains a concrete bug report or actionable feature request.

Suggested action

Close 6261 as a duplicate of 6154. Both are general design-philosophy questions with no actionable content; 6154 is older and slightly broader in scope. Point the author of 6261 to the MicroPython documentation on differences from CPython (docs/differences) and the project's stated design goals.

MicroPython compatability issue with CPython

Why MicroPython isn't tailored from CPython

Keyboard