CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.9.4 2018-05-10T13:00:04+00:00 2018-05-10T13:00:04+00:00 Damien George damien.p.george@gmail.com 2018-05-10T13:00:04+00:00 urn:sha1:bc87b862fd22afb38ed7392b69474286fa5fe19f This new helper function acts like mp_load_method_maybe but is wrapped in an NLR handler so it can catch exceptions. It prevents AttributeError from propagating out, and optionally all other exceptions. This helper can be used to fully implement hasattr (see follow-up commit), and also for cases where mp_load_method_maybe is used but it must now raise an exception. 2018-04-04T04:24:03+00:00 Damien George damien.p.george@gmail.com 2018-04-04T04:24:03+00:00 urn:sha1:3f420c0c27bd6daa5af39517925be55b9b9a9ab3 Without the compiler enabled the mp_optimise_value is unused, and the micropython.opt_level() function is not useful, so exclude these from the build to save RAM and code size. 2018-03-30T01:43:38+00:00 Damien George damien.p.george@gmail.com 2018-03-30T01:37:04+00:00 urn:sha1:f50b64cab58025e080f994147b75a8ffc55d2b35 The VM expects that, if mp_resume() returns MP_VM_RETURN_EXCEPTION, then the returned value is an exception instance (eg to add a traceback to it). It's possible that a value passed to a generator's throw() is not an exception so must be explicitly checked for if the thrown value is not intercepted by the generator. Thanks to @jepler for finding the bug. 2018-03-30T00:13:32+00:00 Damien George damien.p.george@gmail.com 2018-03-30T00:09:00+00:00 urn:sha1:32807881954f106b9735de74fe984062a0815b81 Prior to this patch the code would crash if a key in a ** dict was anything other than a str or qstr. This is because mp_setup_code_state() assumes that keys in kwargs are qstrs (for efficiency). Thanks to @jepler for finding the bug. 2018-02-27T04:48:09+00:00 Damien George damien.p.george@gmail.com 2018-02-27T04:48:09+00:00 urn:sha1:a9f6d4921829195d7310aa8b07a4a705577161a5 There's no need to have MP_OBJ_NULL a special case, the code can re-use the MP_OBJ_STOP_ITERATION value to signal the special case and the VM can detect this with only one check (for MP_OBJ_STOP_ITERATION). 2018-02-20T07:00:44+00:00 Damien George damien.p.george@gmail.com 2018-02-20T07:00:44+00:00 urn:sha1:209936880df4d63730ea77cf4b6f84e5f2f56d7c The new option is MICROPY_ENABLE_EXTERNAL_IMPORT and is enabled by default so that the default behaviour is the same as before. With it disabled import is only supported for built-in modules, not for external files nor frozen modules. This allows to support targets that have no filesystem of any kind and that only have access to pre-supplied built-in modules implemented natively. 2017-12-19T02:13:21+00:00 Damien George damien.p.george@gmail.com 2017-12-19T02:13:21+00:00 urn:sha1:f5fb68e94fe72a7d8c158a47c2374ee0cea0227c 2017-12-11T02:49:09+00:00 Damien George damien.p.george@gmail.com 2017-11-26T12:48:23+00:00 urn:sha1:30fd8484ebe41faad467fbc8dd4a6f72250f203c With MICROPY_ENABLE_PYSTACK enabled the following language constructs no longer allocate on the heap: f(*arg), f(**kwarg). 2017-12-11T02:49:09+00:00 Damien George damien.p.george@gmail.com 2017-11-26T12:37:19+00:00 urn:sha1:1e5a33df413bbd8a8aa5bd880be445c684fc5506 2017-12-11T02:49:09+00:00 Damien George damien.p.george@gmail.com 2017-11-26T12:28:40+00:00 urn:sha1:02d830c035aca166d70551e485ccd2d1658189c9 This patch introduces the MICROPY_ENABLE_PYSTACK option (disabled by default) which enables a "Python stack" that allows to allocate and free memory in a scoped, or Last-In-First-Out (LIFO) way, similar to alloca(). A new memory allocation API is introduced along with this Py-stack. It includes both "local" and "nonlocal" LIFO allocation. Local allocation is intended to be equivalent to using alloca(), whereby the same function must free the memory. Nonlocal allocation is where another function may free the memory, so long as it's still LIFO. Follow-up patches will convert all uses of alloca() and VLA to the new scoped allocation API. The old behaviour (using alloca()) will still be available, but when MICROPY_ENABLE_PYSTACK is enabled then alloca() is no longer required or used. The benefits of enabling this option are (or will be once subsequent patches are made to convert alloca()/VLA): - Toolchains without alloca() can use this feature to obtain correct and efficient scoped memory allocation (compared to using the heap instead of alloca(), which is slower). - Even if alloca() is available, enabling the Py-stack gives slightly more efficient use of stack space when calling nested Python functions, due to the way that compilers implement alloca(). - Enabling the Py-stack with the stackless mode allows for even more efficient stack usage, as well as retaining high performance (because the heap is no longer used to build and destroy stackless code states). - With Py-stack and stackless enabled, Python-calling-Python is no longer recursive in the C mp_execute_bytecode function. The micropython.pystack_use() function is included to measure usage of the Python stack.