-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make user-visible types public to support type hints #461
Comments
I think we should turn Something like this:
The public types would be:
|
Completed refactoring work for task and its submodules, documentation is updated accordingly. Closing this issue. |
Some of the types in nidaqmx.system are not public yet. Also, the docs refer to nonexistent modules like nidaqmx.system.collections and nidaqmx.system.device_collection: (This is really nidaqmx.system._collections, which is private.) |
@bkeryan The things needed to update are:
Anything else i miss out? |
Also make
However, it's confusing that you can import It would make sense to shorten
I think you should turn
(Or you can rename |
The task subobject types (AIChannel, Timing, etc.) are defined in internal modules contained in the private
nidaqmx._task_modules
package. When users write helper functions that accept channel objects or other task subobjects, they must refer to these internal modules. We should make these modules public and/or add public aliases for their types.@StSav012 brought this up in #458
The text was updated successfully, but these errors were encountered: