Christoph Buchner

All good points! Yes, device-specific measured would be implemented in the concrete subclass, and we make sure that that is automatically called by the `shutdown()` method. Exit/interruption-safe handling could be...

I agree with all you said (except for the last paragraph). I think what I argued back then (and now) is that, if all we want to add is interruptability,...

I think an improved test method related to our instrument-related usage would be something like the following run method: ``` def run(self): try: while not self.should_stop(): print('working') sleep(0.1) except Exception:...

@msmttchr do you possibly have an opportunity for a review some time? Unforunately, it's a large (700 line) review, and I can't seem to find enough time to sit down,...

> I'm inclined to vote for keeping the linewidth at 1 and adding the option to change it and a note that users can turn on openGL. This sounds best...

Thanks for the PR! This issue is in fact _not_ closed, though. Its objective is to revert back to a default line width >1 (or at least reassess if that's...

The read_termination/write_termination problem is equivalent to #334, see #409. I think maybe nobody used the instrument yet with a telnetadapter, so this has not appeared yet. For your second problem,...

Judging from > allow storing information (e.g. the actual starting time, instrument parameters) about the measurement I think "Metadata" -- data _about_ something -- would be a good fit. Or...

You could use the fget arg for that -- if it's a method object, call it. If it's a string, try to call the respective method, in an except try...

OP: This is a good thought, and (in some ways) the thinking behind the IVI (Interchangeable Virtual Instrument) standard. Some of these ideas exist in https://github.com/python-ivi/python-ivi, but this is sadly...