9b80a1e3e9
* Fix mis-spelling of `ticks_add` in code examples. * Be consistent about parentheses after function names. * Be consistent about formatting of function, variable and constant names. * Be consistent about spaces and punctuation. * Fix some language errors (missing or wrong words, wrong word order). * Keep line length under 90 chars. Signed-off-by: Christopher Arndt <chris@chrisarndt.de> |
||
---|---|---|
.. | ||
differences | ||
esp8266 | ||
library | ||
pyboard | ||
readthedocs/settings | ||
reference | ||
sphinx_selective_exclude | ||
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> 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
.
PDF manual generation
This can be achieved with:
make MICROPY_PORT=<port_name> latexpdf
but require rather complete install of LaTeX with various extensions. On Debian/Ubuntu, try (500MB+ download):
apt-get install texlive-latex-recommended texlive-latex-extra