CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.6 2015-11-03T23:28:53+00:00 2015-11-03T23:28:53+00:00 Dave Hylands dhylands@gmail.com 2015-11-01T00:48:46+00:00 urn:sha1:a9f3030371094e3308b4d2150853db2ee3aa4a6b 2015-11-03T23:28:27+00:00 Dave Hylands dhylands@gmail.com 2015-11-01T00:46:19+00:00 urn:sha1:98fb0bf68a251741e341c3bfa74cc64f8a238c20 2015-11-03T21:54:56+00:00 Mike Bryant mike@mikebryant.me.uk 2015-11-03T16:22:43+00:00 urn:sha1:1bfa6ae6e45368a441271e11d4b0e3aa343b2c9d 2015-10-30T22:32:48+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2015-10-30T22:32:48+00:00 urn:sha1:3833d3846db1e736a3b27455033dc7cc8939f828 2015-10-20T23:56:42+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2015-10-20T22:52:34+00:00 urn:sha1:9d7ef05caf614bdf862b8c4484c69e794231a51c 2015-10-11T23:15:41+00:00 nyov nyov@nexnode.net 2015-08-12T17:51:01+00:00 urn:sha1:fccbe9aa4d83669d15d0109c604f66d1a4792421 2015-10-11T23:06:25+00:00 Damien George damien.p.george@gmail.com 2015-10-11T23:06:25+00:00 urn:sha1:0334058fa43a8ac7c689007f5824510c2927c5cc 2015-08-22T20:56:28+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2015-08-22T20:56:28+00:00 urn:sha1:5ab0a4a67167a26838ee4ad5305b8dc27d216830 Also, hint about possibility to adjust heap size. 2015-08-17T11:51:26+00:00 Damien George damien.p.george@gmail.com 2015-08-14T11:24:11+00:00 urn:sha1:65dc960e3b22a8426e369607e47c19b380ce30ea unix-cpy was originally written to get semantic equivalent with CPython without writing functional tests. When writing the initial implementation of uPy it was a long way between lexer and functional tests, so the half-way test was to make sure that the bytecode was correct. The idea was that if the uPy bytecode matched CPython 1-1 then uPy would be proper Python if the bytecodes acted correctly. And having matching bytecode meant that it was less likely to miss some deep subtlety in the Python semantics that would require an architectural change later on. But that is all history and it no longer makes sense to retain the ability to output CPython bytecode, because: 1. It outputs CPython 3.3 compatible bytecode. CPython's bytecode changes from version to version, and seems to have changed quite a bit in 3.5. There's no point in changing the bytecode output to match CPython anymore. 2. uPy and CPy do different optimisations to the bytecode which makes it harder to match. 3. The bytecode tests are not run. They were never part of Travis and are not run locally anymore. 4. The EMIT_CPYTHON option needs a lot of extra source code which adds heaps of noise, especially in compile.c. 5. Now that there is an extensive test suite (which tests functionality) there is no need to match the bytecode. Some very subtle behaviour is tested with the test suite and passing these tests is a much better way to stay Python-language compliant, rather than trying to match CPy bytecode. 2015-06-22T17:06:12+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2015-06-21T21:48:21+00:00 urn:sha1:fe99ea9aabb1916581441b850fee6e0888bf1af4 Also, simplify dependencies info now that we no longer require GNU readline.