CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=v1.8.1 2016-05-20T18:18:49+00:00 2016-05-20T18:18:49+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-20T18:16:58+00:00 urn:sha1:497660fcda77ae819f5ea1f6a92b8fb5006d8213 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-04-10T11:41:28+00:00 Damien George damien.p.george@gmail.com 2016-04-10T11:41:28+00:00 urn:sha1:358e5d8bada558e7197f59221989ff6357a915e4 2016-04-10T11:37:59+00:00 Damien George damien.p.george@gmail.com 2016-04-10T11:37:59+00:00 urn:sha1:657aef66ff3cc308155ea1519ae0c701b326033a Saves 16 bytes of code. Also, use mp_obj_get_int_truncated to allow integers as big as a machine word to be passed as the value. 2016-04-10T10:36:44+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-04-10T10:36:44+00:00 urn:sha1:558fd5d228d3c610958c4aae41b1ede0b6487c35 2016-04-10T10:31:52+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-04-10T10:31:52+00:00 urn:sha1:6c3db26ab7e03fa0140fb8d3ed315e69717b59ca 2016-04-10T09:45:46+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-04-10T09:45:46+00:00 urn:sha1:0c97e4c4144565ca3b18593d708f0d7a94905c71 Will call underlying C virtual methods of stream interface. This isn't intended to be added to every stream object (it's not in CPython), but is convenient way to expose extra operation on Python side without adding bunch of Python-level methods. 2016-03-27T09:58:33+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-27T09:58:33+00:00 urn:sha1:53ad5edc01aee3d469feaaafa389be3d686548bb 2016-03-24T17:43:08+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-24T17:43:08+00:00 urn:sha1:4a02a8f74ddec92369d8bf2bd51e4191d0d42c5c 2016-03-24T17:09:00+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-03-24T17:09:00+00:00 urn:sha1:d4c8e626f280ab096c1341577931d8071972bd4c Spools entire output buffer to a blocking stream (chunk by chunk if needed).