Season of Docs : MicroPython

[pythoncoder]

...
One tricky issue is that different ports of MicroPython come with different set of modules which may include different functions. It would be great if the documentation work done on one port could be reused and tweaked for other ports...

I have developed a number of modules for MicroPython intended for general use across platforms. The task has become progressively harder as the number of platforms has increased. It is now virtually impossible to guarantee cross-platform operation because the ports have different features, a difference which is undocumented. I raised this RFC on the subject.

I appreciate that there are inevitable hardware issues. But you can't even guarantee that pure Python code will work cross-platform because core language features can be missing. This even applies to the Unix port, which I find baffling given that the original Raspberry Pi 1 had 500MB of RAM.

In response to the RFC, @Damien suggested a good solution. I suggest that anyone working on the docs might want to consider this issue.

[v923z]

@jnanjeky I think, some of what you want to write up is already in https://micropython-usermod.readthedocs.io/en/latest/.

[jnanjeky]

Yes, some of the information on internals is not so new. Its about recollecting relevant parts and added missing areas on the interpreter itself.

[hlovatt]

I have generated a couple of typesheds (type hint interfaces): `pyb.pyi` and `uarray.pyi`. The files are at https://github.com/hlovatt/PyBoardTypeshed and the code used to generate them is at https://github.com/hlovatt/PyBoardTypeshedGenerator. These are helpful for IDEs that understand types and/or show documentation: PyCharm, VSCode, etc.