It cannot be fully backported because some features of Python 3.x are used. But most of the functionality can be backported, although it won’t be done officially since there isn’t going to be Python version 2.8 (see http://www.python.org/dev/peps/pep-0404/)

Actually most modern styles advocate the opening brace on the same line in class and funtion definitions as well. I’m not sure whether this was part of the original K&R standard.

Meanwhile all the *drawbacks* you listed are real, plus the most obvious drawback of braces no longer lining up.

Just don’t see the appeal.

With TCO you effectively have only one caller and you don’t have to return to it. This is true regardless of the amount of calls (or state transitions). If you do it in a new thread of control (with an independent stack) you don’t even have to have a caller (you can tail-call immediately from the entry function).

Delimited continuations are like threads (serializable threads, so you can do multiple resumes). Full-blown continuations are similar but when you capture the continuation you do something fork()-like instead of just “serializing” a thread with a well defined starting point.

def write_data(self, data):
    self.serial_port.write(data)

call it from plotting_data_monitor

self.com_monitor.write_data("Hello\n")