CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=esp-extra-scripts 2016-08-07T19:36:05+00:00 2016-08-07T19:36:05+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-08-07T19:36:05+00:00 urn:sha1:1bc2911174aa975bbcb15cd70dd2dabfc7c8c535 Similar to existing MP_NOINLINE. 2016-08-07T03:46:55+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-08-07T03:46:55+00:00 urn:sha1:56eb25f04928132f9921a1163684e626256e2a2c Default is disabled, enabled for unix port. Saves 600 bytes on x86. 2016-07-30T17:05:56+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-30T17:05:56+00:00 urn:sha1:61e77a4e88c4b6971fd997191de01e5ab08e46c5 To filter out even prototypes of mp_stream_posix_*() functions, which require POSIX types like ssize_t & off_t, which may be not available in some ports. 2016-07-21T21:46:24+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-21T21:46:24+00:00 urn:sha1:a1b442bc07798afb774acaaef391443d76104543 2016-07-21T21:34:34+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-21T21:34:34+00:00 urn:sha1:707cae749424104660cd24e7c1f1e16d67b99b0f Something like: if foo == "bar": will be always false if foo is b"bar". In CPython, warning is issued if interpreter is started as "python3 -b". In MicroPython, MICROPY_PY_STR_BYTES_CMP_WARN setting controls it. 2016-07-20T21:37:30+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-20T21:37:30+00:00 urn:sha1:93e353e3844f7116088a1a105ba588cade0e6783 Currently, MicroPython runs GC when it could not allocate a block of memory, which happens when heap is exhausted. However, that policy can't work well with "inifinity" heaps, e.g. backed by a virtual memory - there will be a lot of swap thrashing long before VM will be exhausted. Instead, in such cases "allocation threshold" policy is used: a GC is run after some number of allocations have been made. Details vary, for example, number or total amount of allocations can be used, threshold may be self-adjusting based on GC outcome, etc. This change implements a simple variant of such policy for MicroPython. Amount of allocated memory so far is used for threshold, to make it useful to typical finite-size, and small, heaps as used with MicroPython ports. And such GC policy is indeed useful for such types of heaps too, as it allows to better control fragmentation. For example, if a threshold is set to half size of heap, then for an application which usually makes big number of small allocations, that will (try to) keep half of heap memory in a nice defragmented state for an occasional large allocation. For an application which doesn't exhibit such behavior, there won't be any visible effects, except for GC running more frequently, which however may affect performance. To address this, the GC threshold is configurable, and by default is off so far. It's configured with gc.threshold(amount_in_bytes) call (can be queries without an argument). 2016-07-02T11:57:42+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-02T11:57:42+00:00 urn:sha1:737bd9c3144a57673db8b02217114b7f7f63387d However, as it requires linking with external libraries, it actually should be ste on Makefile level. 2016-06-28T10:28:50+00:00 Damien George damien.p.george@gmail.com 2016-05-26T10:42:53+00:00 urn:sha1:4cec63a9dbed86c4332b9e7fcd56d092046193e4 This makes the VM/runtime thread safe, at the cost of not being able to run code in parallel. 2016-06-28T10:28:48+00:00 Damien George damien.p.george@gmail.com 2016-04-22T22:52:33+00:00 urn:sha1:27cc07721b3c3c2d0b9c8678c8a3ddc7fe96cd97 2016-06-15T20:52:00+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-06-15T20:52:00+00:00 urn:sha1:0f5bf1aafe0ca073d958f271bd96addc6da8fe10