for computer use

[ladyada]

CPython is pickier about unpack lenghts, and requires a flush on no-end prints

[ladyada]

this one didn't have any byte/string issues cause its all data anyhow, but did need some CPythonification

[dhalbert]

See comment question re print(..., flush=True)

[dhalbert]

In CircuitPython 3.x, extra keyword args to print() are ignored. In 4.0, because of a merge we did from MicroPython, they are now checked, but flush= is not an implemented keyword arg, and fails in 4.0:

Adafruit CircuitPython 4.0.0-alpha-922-g9da79c880-dirty on 2018-08-19; Adafruit Metro M0 Express with samd21g18
>>> print("abc", "def", sep=".")
abc.def
>>> print("abc", "def", sepx=".")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: extra keyword arguments given
>>> print("abc", "def", end=".")
abc def.>>> print("abc", "def", flush=True)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: extra keyword arguments given
>>> 

So we need to handle flush in 4.0, otherwise this code will fail.

Not sure if any reasonable change can be made in this library. Seems like I should open an issue for 4.0.0

[ladyada]

yah plz do, but i think we should default to True - basically CPython wont actually emit the output otherwise. kinda lame!

[ladyada]

or rather, there probably isnt a way for us to False not-flush. i dunno. we can ignore it but have the kwarg there? up to y'all

[dhalbert]

@tannewt have a comment here?

[dhalbert]

An alternative here is just to print each of those status messages on their own lines (remove end="").

[ladyada]

always an option, but it makes for a nice UI to keep :)