CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=esp-extra-scripts 2016-08-06T21:01:25+00:00 2016-08-06T21:01:25+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-08-06T21:01:25+00:00 urn:sha1:e15fb33e109983ced35f14c674e0aa1d47dbc357 2016-08-05T19:57:50+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-08-05T19:57:50+00:00 urn:sha1:ed500e49878292c87cd68b8fcfd842f70201eb2d In the sense that while GET_FILE transfers its data, REPL still works. This is done by requiring client to send 1-byte block before WebREPL server transfers next block of data. 2016-08-05T19:53:10+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-08-05T19:53:10+00:00 urn:sha1:c16612ee87e2f3c58ef26031dc04b689da772c51 2016-07-22T21:52:35+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-22T21:52:35+00:00 urn:sha1:2dd21d9a68ef90bd42fa355a744dde89031611c1 2016-07-02T11:05:37+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-07-02T11:05:37+00:00 urn:sha1:c880f91ac0d5157c23a78e5e9739388b57419e5d 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-20T18:32:41+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-20T18:32:41+00:00 urn:sha1:3a29db8e58d963747697025e847444430c9f8b9e 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-02T17:52:34+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-05-02T17:52:34+00:00 urn:sha1:b8468d12a1a35eececff6432349dc0f66b10d3dd 2016-04-30T17:36:32+00:00 Paul Sokolovsky pfalcon@users.sourceforge.net 2016-04-29T21:57:56+00:00 urn:sha1:859e4e94f3f3f69e00c8b8c910461fa036eaf649 Request for password then becomes mandatory part of the protocol.