CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=main 2015-08-17T11:51:26+00:00 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-01-01T20:41:52+00:00 Damien George damien.p.george@gmail.com 2015-01-01T20:41:52+00:00 urn:sha1:b36be5ff5172c97a8f37228c1ec163df466fd588 2014-12-27T14:32:52+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2014-12-27T14:11:49+00:00 urn:sha1:3b74c91684e6dfc785bf33ba03e520470f59059e 2014-10-29T09:29:09+00:00 stijn stinos@zoho.com 2014-10-29T09:05:55+00:00 urn:sha1:4e54c876a7236cbb50431f1f6d52c7be2052ed6f 2014-04-17T17:03:27+00:00 Damien George damien.p.george@gmail.com 2014-04-17T17:03:27+00:00 urn:sha1:d553be5982722fc5ee5240fbfb15697849881ced Any generated headers go in $(BUILD)/genhdr/, and are #included as 'genhdr/xxx.h'. 2014-04-16T21:16:28+00:00 Andrew Scheller github@loowis.durge.org 2014-04-16T21:10:33+00:00 urn:sha1:70a7d7a94397cbe01fd5457e34f3d3368300f2ac The autogenerated header files have been moved about, and an extra include dir has been added, which means you can give a custom BUILD=newbuilddir option to make, and everything "just works" Also tidied up the way the different Makefiles build their include- directory flags 2014-01-26T17:52:23+00:00 Damien George damien.p.george@gmail.com 2014-01-26T17:52:23+00:00 urn:sha1:56bb636014aaab4ac5dfada6b80fe5c2de820d34 2014-01-24T16:46:48+00:00 Dave Hylands dhylands@gmail.com 2014-01-24T09:05:30+00:00 urn:sha1:c89c681a9f065e66ce817a024fda24abeed9519f 2014-01-21T21:40:13+00:00 Damien George damien.p.george@gmail.com 2014-01-21T21:40:13+00:00 urn:sha1:55baff4c9bcbc001cbb8972c289ebfa356d4665b Can now have null bytes in strings. Can define ROM qstrs per port using qstrdefsport.h 2014-01-15T22:58:39+00:00 Damien George damien.p.george@gmail.com 2014-01-15T22:58:39+00:00 urn:sha1:5573f9f150d513ed3f996722e2b57b58cfb24f3b Conflicts: py/objint.c unix-cpy/Makefile unix/Makefile