Christoph Buchner

Thank you for your input! > since instrument driver should be separated from application. Well, the driver is still separate from the application. The application uses the driver to create...

So, you're rich and have two Fiat 500 XL, one red ("Il lampo rosso") and one white ("Innocenza"), and you want to take the red lightning out for a spin....

And yes, I had a situation/setup where there were 3 (I think) power supplies for 3 different aspects of the experiment, I did not have individual variable names available (they...

Side remark: class or instance property does not make much of a difference. If `Instrument.name` were a class property, as soon as we change it (e.g. in an initialiser) it...

I think on the point of name intended to be fixed, we just have to disagree. > making the code more obscure and difficult to read Concerning this, is this...

I'm still reproducing this issue using ipykernel 6.2.0 and notebook 6.4.3 (on Windows) Actually, it seems to have grown worse, since the stated workaround > If you instead interrupt the...

I can recommend [pytest](https://docs.pytest.org/en/latest/nose.html). If you have a working test configuration, typically calling `pytest` instead of `nose` just works. See also [docs](https://docs.pytest.org/en/latest/nose.html) concerning this.

Sphinx seems like a solid choice.

Does this still apply? And what does "not work" mean for you? I am currently using the extension in a [Dev container via Docker](https://code.visualstudio.com/docs/remote/containers-tutorial) on Windows, and it does work,...

This is just a drive-by comment by a scientific python user, but I would definitely try to avoid confusion with `sympy.lambdify`, especially if you don't plan on reaching feature parity...