CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.9.2 2017-07-31T08:35:40+00:00 2017-07-31T08:35:40+00:00 Alexander Steffen devel.20.webmeister@spamgourmet.com 2017-06-30T07:22:17+00:00 urn:sha1:55f33240f3d7051d4213629e92437a36f1fac50e There were several different spellings of MicroPython present in comments, when there should be only one. 2015-11-29T14:25:35+00:00 Damien George damien.p.george@gmail.com 2015-11-27T17:01:44+00:00 urn:sha1:999cedb90ff0827cdb9dfe0e4faa6ebc1739d271 This allows the mp_obj_t type to be configured to something other than a pointer-sized primitive type. This patch also includes additional changes to allow the code to compile when sizeof(mp_uint_t) != sizeof(void*), such as using size_t instead of mp_uint_t, and various casts. 2015-09-15T21:46:30+00:00 Tom Soulanille soul@prama.com 2015-09-15T21:30:52+00:00 urn:sha1:661d9d1901d3afcc9fdee7e4ab7cfd17688cb7d0 2015-09-15T20:59:20+00:00 Tom Soulanille soul@prama.com 2015-09-11T21:31:32+00:00 urn:sha1:aeb62f9ae3169d789800591eea390e020c7532bf Configurable with MICROPY_PY_BUILTINS_SLICE_ATTRS. Disabled by default. 2015-05-05T19:18:07+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2015-05-05T19:18:07+00:00 urn:sha1:76677270218fb5732296e4fe1a0acbe05c8f818c Having NotImplemented as MP_OBJ_SENTINEL turned out to be problematic (it needs to be checked for in a lot of places, otherwise it'll crash as would pass MP_OBJ_IS_OBJ()), so made a proper singleton value like Ellipsis, both of them sharing the same type. 2015-04-16T14:30:16+00:00 Damien George damien.p.george@gmail.com 2015-04-09T22:56:15+00:00 urn:sha1:7f9d1d6ab923096582622b700bedb6a571518eac Previous to this patch the printing mechanism was a bit of a tangled mess. This patch attempts to consolidate printing into one interface. All (non-debug) printing now uses the mp_print* family of functions, mainly mp_printf. All these functions take an mp_print_t structure as their first argument, and this structure defines the printing backend through the "print_strn" function of said structure. Printing from the uPy core can reach the platform-defined print code via two paths: either through mp_sys_stdout_obj (defined pert port) in conjunction with mp_stream_write; or through the mp_plat_print structure which uses the MP_PLAT_PRINT_STRN macro to define how string are printed on the platform. The former is only used when MICROPY_PY_IO is defined. With this new scheme printing is generally more efficient (less layers to go through, less arguments to pass), and, given an mp_print_t* structure, one can call mp_print_str for efficiency instead of mp_printf("%s", ...). Code size is also reduced by around 200 bytes on Thumb2 archs. 2015-01-20T12:47:20+00:00 Damien George damien.p.george@gmail.com 2015-01-20T12:47:20+00:00 urn:sha1:ff8dd3f486afb0d6ff1427d8a6a8a8ed73baa660 See issue #699. 2015-01-01T20:32:09+00:00 Damien George damien.p.george@gmail.com 2015-01-01T20:27:54+00:00 urn:sha1:51dfcb4bb7613ed164952712d9a5235a7b833cde Addresses issue #1022. 2014-12-10T22:08:14+00:00 Damien George damien.p.george@gmail.com 2014-12-10T22:07:04+00:00 urn:sha1:969a6b37bfc655609e540053c2bdcce8a6fdc64d 2014-06-01T12:32:54+00:00 Damien George damien.p.george@gmail.com 2014-06-01T12:32:54+00:00 urn:sha1:fb510b3bf90eccc8e0d400c6622b2e94c2bfa8e9 This renames: MICROPY_PY_FROZENSET -> MICROPY_PY_BUILTINS_FROZENSET MICROPY_PY_PROPERTY -> MICROPY_PY_BUILTINS_PROPERTY MICROPY_PY_SLICE -> MICROPY_PY_BUILTINS_SLICE MICROPY_ENABLE_FLOAT -> MICROPY_PY_BUILTINS_FLOAT See issue #35 for discussion.