CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=main 2018-05-14T18:02:25+00:00 2018-05-14T18:02:25+00:00 Karin Hawley karin@joinhonor.com 2018-05-14T17:32:01+00:00 urn:sha1:f9ae1ee1729b16a2459a93f1c777f851e0418a6b - moving Makefile to parent folder. This resolves some of the weird path/build issues - remove trace references to cpydiff and original file (no longer used anywhere) - converting SOURCEDIR to a changeable variable, passed through all sphinx-build calls - adding path to conf.py, in case it moves again - making `-v` default with VERBOSE - making `-E` default with FORCE - creating BASEOPTS to store all the dirs, paths, and settings, passing them to sphinx-build in one long chain, instead of individually - updating README to use the make command as default. Also added text explaining some of the customization you can add into a make command 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2017-07-09T10:51:40+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2017-07-09T10:51:40+00:00 urn:sha1:ad5e7a0e6f991e923fe94cce444289252304f589 This is required to easily giving links to a particular difference case. Also, add RST anchors to allow cases to cross-reference each other. 2017-02-27T04:39:55+00:00 Krzysztof Blazewicz blazewicz.krzysztof@gmail.com 2017-02-25T12:53:56+00:00 urn:sha1:23ccb3e12e3b7fe6b56785d1e17e9d990d1da86c 2017-02-22T04:50:58+00:00 Damien George damien.p.george@gmail.com 2017-02-22T04:50:58+00:00 urn:sha1:1034d9acc84317b21b953d3e9fd6ad5519d1c570 2017-02-20T06:14:34+00:00 Rami Ali flowergrass@users.noreply.github.com 2017-02-07T05:43:41+00:00 urn:sha1:b7fa63c7ced460fd2d3aceb35257a62ff08831c1 This patch introduces the a small framework to track differences between uPy and CPython. The framework consists of: - A set of "tests" which test for an individual feature that differs between uPy and CPy. Each test is like a normal uPy test in the test suite, but has a special comment at the start with some meta-data: a category (eg syntax, core language), a human-readable description of the difference, a cause, and a workaround. Following the meta-data there is a short code snippet which demonstrates the difference. See tests/cpydiff directory for the initial set of tests. - A program (this patch) which runs all the tests (on uPy and CPy) and generates nicely-formated .rst documenting the differences. - Integration into the docs build so that everything is automatic, and the differences appear in a way that is easy for users to read/reference (see latter commits). The idea with using this new framework is: - When a new difference is found it's easy to write a short test for it, along with a description, and add it to the existing ones. It's also easy for contributors to submit tests for differences they find. - When something is no longer different the tool will give an error and difference can be removed (or promoted to a proper feature test).