492bf12499
Even the modules whose names don't start with "u" prefix are micro-ified anyway, i.e. provide only subset of CPython's functionality (and sometimes extensions to it). So, it doesn't make much sense to devide them by criteria of having/not having "u" prefix. |
||
|---|---|---|
| .. | ||
| esp8266 | ||
| library | ||
| pyboard | ||
| readthedocs/settings | ||
| reference | ||
| static | ||
| templates | ||
| wipy | ||
| conf.py | ||
| esp8266_contents.rst | ||
| esp8266_index.rst | ||
| license.rst | ||
| make.bat | ||
| Makefile | ||
| pyboard_contents.rst | ||
| pyboard_index.rst | ||
| README.md | ||
| topindex.html | ||
| unix_contents.rst | ||
| unix_index.rst | ||
| wipy_contents.rst | ||
| wipy_index.rst | ||
MicroPython Documentation
The MicroPython documentation can be found at: http://docs.micropython.org/en/latest/
The documentation you see there is generated from the files in the docs tree: https://github.com/micropython/micropython/tree/master/docs
Building the documentation locally
If you're making changes to the documentation, you may want to build the documentation locally so that you can preview your changes.
Install Sphinx, and optionally (for the RTD-styling), sphinx_rtd_theme, preferably in a virtualenv:
pip install sphinx
pip install sphinx_rtd_theme
In micropython/docs, build the docs:
make MICROPY_PORT=<port_name> BUILDDIR=build/<port_name> html
Where <port_name> can be unix, pyboard, wipy or esp8266.
You'll find the index page at micropython/docs/build/<port_name>/html/index.html.