Brad Keryan

Before doing anything here, check https://github.com/actions/upload-artifact/issues/472 for updated guidance on how to solve this.

BTW, providing public type aliases for `Channel`, `Instrument`, `Pin`, `Site`, etc. would be a relatively easy solution. ```python Channel = _SessionBase Instrument = _SessionBase ... ```

Note that `_SessionBase` is in `nidcpower.session` and not aliased into `nidcpower`, so the example code above is incorrect.

Note that `windows-1251` is for languages that use Cyrillic script, such as Russian, Ukrainian, and Belarusian. You probably meant to hardcode `windows-1252`, which is roughly equivalent to Latin-1.

@ni-jfitzger Are you referring to the .NET API? C and LV have `niSwitch_InitWithOptions` which supports specifying the topology as well as other options.

The collection types are really not a big deal. They don't even require the `typing_extensions` package. For now, use `from typing import List` and write `List[T]`. When you drop Python...

The gRPC C Core's policy on reusing client contexts hasn't changed and is unlikely to change. The assertion is still present: https://github.com/grpc/grpc/blob/master/src/cpp/client/client_context.cc#L128 grpc_client.cc doesn't seem to have any code for...

LabVIEW 2019 SP1 (64-bit) has the same behavior.

`Create Message Data Clusters (simple).vi` assumes the `RPC Messages` virtual folder already exists. If I delete it from the project, then `Create Client from Template.vi` doesn't re-create it because the...

I think we should turn `task.py` into a package, merge it with `_task_modules`, make most of the submodules private, and add aliases to reexport types from the subpackages. Something like...