CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=0.8.2 2016-10-07T02:31:59+00:00 2016-10-07T02:31:59+00:00 Damien George damien.p.george@gmail.com 2016-10-07T02:31:59+00:00 urn:sha1:3a0a7717304cc34a4d6ef55f767666c918c185b5 This is an often used code pattern, and its use reduces code size of the core by about 100 bytes. 2016-09-21T14:23:16+00:00 Damien George damien.p.george@gmail.com 2016-09-21T00:52:53+00:00 urn:sha1:93c4a6a3f70e389b466fbc7a4f1ad2e1df87c93f One can instead lookup __name__ in the modules dict to get the value. 2016-06-18T15:44:57+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-06-18T15:19:24+00:00 urn:sha1:07209f8592f15435d6abbccaad5347cea2c7722e It's now used for more than just stream protocol (e.g. pin protocol), so don't use false names. 2016-05-17T23:41:45+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-17T23:40:03+00:00 urn:sha1:7f7c84b10a5f3b2f783955b01f55e0f913ac459f Both read and write operations support variants where either a) a single call is made to the undelying stream implementation and returned buffer length may be less than requested, or b) calls are repeated until requested amount of data is collected, shorter amount is returned only in case of EOF or error. These operations are available from the level of C support functions to be used by other C modules to implementations of Python methods to be used in user-facing objects. The rationale of these changes is to allow to write concise and robust code to work with *blocking* streams of types prone to short reads, like serial interfaces and sockets. Particular object types may select "exact" vs "once" types of methods depending on their needs. E.g., for sockets, revc() and send() methods continue to be "once", while read() and write() thus converted to "exactly" versions. These changes don't affect non-blocking handling, e.g. trying "exact" method on the non-blocking socket will return as much data as available without blocking. No data available is continued to be signaled as None return value to read() and write(). From the point of view of CPython compatibility, this model is a cross between its io.RawIOBase and io.BufferedIOBase abstract classes. For blocking streams, it works as io.BufferedIOBase model (guaranteeing lack of short reads/writes), while for non-blocking - as io.RawIOBase, returning None in case of lack of data (instead of raising expensive exception, as required by io.BufferedIOBase). Such a cross-behavior should be optimal for MicroPython needs. 2016-05-02T10:56:33+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-02T10:56:33+00:00 urn:sha1:ddb9dba2f73e6bc62326fe1aad88cdf633358d82 2016-03-25T12:59:30+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-25T12:59:30+00:00 urn:sha1:2c81b9be28dccf973b7c3a7d791ba79ebad6b206 2016-03-25T12:33:38+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-25T12:33:38+00:00 urn:sha1:063e6e7d0aa6fa6ad9f9c65cac4eb49e4a5a6548 2016-03-24T23:10:49+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-24T23:10:49+00:00 urn:sha1:5d93dfbc2cca21806970d3a6a26b488191703f0b Just .write() method implemented currently. 2015-11-29T14:25:04+00:00 Damien George damien.p.george@gmail.com 2015-11-27T13:38:15+00:00 urn:sha1:cbf7674025814797f5c537d6d1c195efe58ccaaf 2015-02-15T13:17:11+00:00 Damien George damien.p.george@gmail.com 2015-02-15T13:17:11+00:00 urn:sha1:e5039c6ff887dfbee84e7853defda2b18722e24c