RFC: MICROPY_PY_BUILTINS_NEXT2 always set to (0) ?
Current settings for all ports break cpython script compatibility on next()
https://docs.python.org/3.5/library/functions.html#next
because
MICROPY_PY_BUILTINS_NEXT2 is never defined to 1 except in coverage and defaults to 0
https://github.com/micropython/micropython/blob/master/py/mpconfig.h#L910
Conventions for MicroPython->CPython compatibility modules
The implementation of this probably belongs to micropython-lib, but as we have more people here, I post RFC here.
So, as we go forward, uPy offers more and more features which are not compatible with CPython. But we surely want to remain good members of Python community, and provide a compatibility layer to run MicroPython-optimized programs on other Python implementations. We had beginnings of that for a long time - https://github.com/micropython/micropython/blob/master/examples/micropython.py , and this RFC is to set conventions and guidelines how to go forward with this.
My proposals:
- Host such compatibility modules in micropython-lib repo.
- To distinguish them from native uPy modules, have their dir names prefixed with "cpython-".
- For PyPi, stick with existing convention of "micropython-" prefix, which them will be followed by "cpython-" infix.
As an example, CPython compatibility shim for MicroPython's "micropython" module will be possible to install from PyPi as "micropython-cpython-micropython".