Zach Hindes

We have been doing this as we've improved code generation and are moving to 1.0.

We aren't planning on adding device calibration support, and these entrypoints were caught up in that decision. I agree that they should be added. There isn't any plan to do...

Sorry, no change. However, you could do this yourself, if you wanted. Under the hood we use ctypes to load the nidaqmx DLL and call functions on it. You can...

Hmm, good catch. We could allow for a NumPy array that is bigger than necessary since `read_many_sample` returns how much data is valid.

I suspect this is related to #161, but we haven't had a chance to figure that one out, yet.

[task.close() closes all open event handlers](https://github.com/ni/nidaqmx-python/blob/3fdfbee7946389c332c58f47af2c25a2b0d6e2c6/generated/nidaqmx/task/_task.py#L360) and then [GrpcEventHandler.close()](https://github.com/ni/nidaqmx-python/blob/3fdfbee7946389c332c58f47af2c25a2b0d6e2c6/generated/nidaqmx/_grpc_interpreter.py#L60) joins its event thread. When calling `task.close` from the event itself, the current thread is the event thread. A thread joining...

@salehcDA - No current plans, sorry.

We have PR/CI actions now. We also have plenty of internal clients as well.

@bkeryan Oh, right, I see. I think our existing (and hopefully soon-to-be-improving) CAPI testing is a good start, but this would be even better. I suspect this won't be a...

@flef - this is a 6-year old Feature request. Nobody here will create a PR with that change. You can if you'd like!