suspect-devices/circuitpython, branch v1.8.2CircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.8.22016-07-10T11:46:50+00:00docs: Bump version to 1.8.2.2016-07-10T11:46:50+00:00Damien Georgedamien.p.george@gmail.com2016-07-10T11:46:50+00:00urn:sha1:1459a8d5c9b29c78da2cf5c7cf3c37ab03b34b8etravis: Run unix thread tests.2016-07-09T15:53:40+00:00Damien Georgedamien.p.george@gmail.com2016-07-09T15:53:40+00:00urn:sha1:56bb6f3979c6f46b5a71a05844718aba1717eccbtests/run-tests: If running thread tests on unix, don't run mutate ones.2016-07-09T15:52:57+00:00Damien Georgedamien.p.george@gmail.com2016-07-09T15:52:57+00:00urn:sha1:2b5a1067c0664836ad8737832754f0866f549fd1
They will fail because the GIL is disabled on the unix build.
unix: Disable the GIL to improve performance of non-thread code.2016-07-09T15:48:06+00:00Damien Georgedamien.p.george@gmail.com2016-07-09T15:48:06+00:00urn:sha1:3096928d5ab6544c3f85639e1b97ac2cefcc2a74
Threading support is still very new so stay conservative at this point
and enable threading without the GIL. This requires users to protect
concurrent access of mutatable Python objects (eg lists) with locks at
the Python level (something you should probably do anyway). The
advantage is that there is less of a performance hit for non-threaded
code, because the VM does not need to constantly release/acquire the GIL.
In the future the GIL will be made more efficient. There is also room to
improve the efficiency of non-GIL code by not using mutex's if there is
only one thread active.
unix/main: When preparing sys.path, allocate exact strings on uPy heap.2016-07-08T22:48:07+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-07-08T22:48:07+00:00urn:sha1:520f35632d78e1b73f647d993205aade0de8b1ce
Due to the way modern compilers work (allocating space for stack vars once
at tha start of function, and deallocating once on exit from), using
intermediate stack buffer of big size caused blockage of 4K (PATH_MAX)
on stack for the entire duration of MicroPython execution.
unix/main: Improve help for -X options a bit.2016-07-08T17:53:08+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-07-08T17:53:08+00:00urn:sha1:649b69a1dbc91c7df8809c4a20c6287b23ac7f52unix/main: Error out on unknown value of suffix in -X heapsize= option.2016-07-08T17:49:41+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-07-08T17:45:15+00:00urn:sha1:0e5e14fe7cd97fa83e822c1e105cf498dbb4d276
E.g. -X heapsize=16Kfoo, -X heapsize=1G will lead to error.
extmod/moduos_dupterm: Reuse dupterm_arr_obj for write operations.2016-07-06T23:16:24+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-07-06T23:16:24+00:00urn:sha1:a4c8a1ffe86ace0b4394d751a2d3716f7d865ba6
Instead of allocating new array object header again and again, causing
memory fragmentation.
py/objarray: Split out header to allow direct access to object.2016-07-06T15:19:27+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-07-06T15:18:46+00:00urn:sha1:ec7fe925312845f788590ce5ccb2a8b3a18a0486
This follows source code/header file organization similar to few other
objects, and intended to be used only is special cases, where efficiency/
simplicity matters.
esp8266/esp_mphal: Properly handle dupterm EOF after switching to readinto().2016-07-05T11:18:12+00:00Paul Sokolovskypfalcon@users.sourceforge.net2016-07-05T11:18:12+00:00urn:sha1:380561836d8d752d55765578506450d7121355b5