pyproject.toml introduction

.github/workflows/validate_python.yml

@@ -27,7 +27,7 @@ jobs:
     - name: Install poetry for validate_examples.py
       uses: abatilo/actions-poetry@v3
       with:
-        poetry-version: 1.2.2
+        poetry-version: 1.8.2
 
     - name: Validate examples (except aio)
       run: |

examples/nifpga/read_write_array_example.py

@@ -1,4 +1,4 @@
-r""" Read and Write to Arrays.
+r"""Read and Write to Arrays.
 
 The gRPC API is built from the C API. NI-FPGA documentation is installed with the driver at:
     C:\Program Files (x86)\National Instruments\FPGA Interface C API\capi.chm

examples/nifpga/read_write_fifo_example.py

@@ -1,4 +1,4 @@
-r""" Read and Write to controls and FIFO.
+r"""Read and Write to controls and FIFO.
 
 The gRPC API is built from the C API. NI-FPGA documentation is installed with the driver at:
     C:\Program Files (x86)\National Instruments\FPGA Interface C API\capi.chm
@@ -7,8 +7,8 @@
 
 To run this example with your VI, you need to configure the values below.
 Additionally, you should have a VI that includes controls and FIFOs, and update the
-references for them below. Ensure that the R-Series drivers are installed on the system 
-where the gRPC-device server is running. You will also need LABVIEW and the LABVIEW FPGA 
+references for them below. Ensure that the R-Series drivers are installed on the system
+where the gRPC-device server is running. You will also need LABVIEW and the LABVIEW FPGA
 module to configure the VIs.
 
 For instructions on how to use protoc to generate gRPC client interfaces, see our "Creating a gRPC
@@ -21,8 +21,8 @@
 If they are not passed in as command line arguments, then by default the server address will be
 "localhost:31763", with "FPGA" as the resource name.
 
-In this example, we specify the number of elements to write to the FIFO and provide 
-a multiplier as input. We then read elements from another FIFO, which contains the multiplied 
+In this example, we specify the number of elements to write to the FIFO and provide
+a multiplier as input. We then read elements from another FIFO, which contains the multiplied
 values of the elements from the first FIFO.
 """
 

examples/nirfmxcdma2k/acp.py

@@ -26,7 +26,7 @@
 To run this example, install "RFmx CDMA2k" on the server machine.
 Link: https://www.ni.com/en-us/support/downloads/software-products/download.rfmx-cdma2k.html
 
-For instructions on how to use protoc to generate gRPC client interfaces, see our "Creating a 
+For instructions on how to use protoc to generate gRPC client interfaces, see our "Creating a
 gRPC Client" wiki page.
 Link: https://github.com/ni/grpc-device/wiki/Creating-a-gRPC-Client
 

examples/nirfmxdemod/ADemod-AM-basic.py

@@ -32,7 +32,6 @@
 "localhost:31763", with "SimulatedDevice" as the resource name
 """
 
-
 import sys
 
 import grpc

examples/nirfmxtdscdma/acp.py

@@ -40,7 +40,6 @@
 "localhost:31763", with "SimulatedDevice" as the resource name
 """
 
-
 import sys
 
 import grpc

examples/nirfmxtdscdma/modacc.py

@@ -37,7 +37,6 @@
 "localhost:31763", with "SimulatedDevice" as the resource name
 """
 
-
 import sys
 
 import grpc

examples/nixnet/can-signal-single-point-output.py

@@ -1,9 +1,9 @@
-r""" Write Signal Data.
+r"""Write Signal Data.
 
  This example writes a signal value for 10 times.
- This is used to demonstrate a signal single point output session. 
+ This is used to demonstrate a signal single point output session.
  This example uses hardcoded signal names that use the NIXNET_example database.
- To use your own database, you need to add an alias to your database file using the NI-XNET 
+ To use your own database, you need to add an alias to your database file using the NI-XNET
  Database Editor and then modify the database name and signals used here.
  Also ensure that the transceivers are externally powered when using C Series modules.
 

examples/nixnet/ethernet-frame-stream-input-reader.py

@@ -1,8 +1,8 @@
-r""" Reads all the frame on network.
+r"""Reads all the frame on network.
 
-  This example reads all the frames on the network and displays them. 
+  This example reads all the frames on the network and displays them.
   This is used to demonstrate a frame input stream session.
-  Ensure that you have connected the selected interface to another Ethernet interface that is 
+  Ensure that you have connected the selected interface to another Ethernet interface that is
   transmitting data.
 
 The gRPC API is built from the C API. NI-XNET documentation is installed with the driver at:

examples/nixnet/flexray-signal-single-point-input.py

@@ -1,8 +1,8 @@
-r""" Read Signal Data.
- 
+r"""Read Signal Data.
+
  This example reads a signal value for 10 times.
- This is used to demonstrate a signal single point input session. 
- This example uses hardcoded signal names that use the NIXNET_example database. 
+ This is used to demonstrate a signal single point input session.
+ This example uses hardcoded signal names that use the NIXNET_example database.
  To use your own database, you need to add an alias to your database file using the NI-XNET
  Database Editor and then modify the database name and signals used here.
  Also ensure that the bus is properly terminated as this example does not enable the on-board
@@ -21,7 +21,7 @@
 
 Refer to the NI XNET gRPC Wiki for the latest C Function Reference:
   https://github.com/ni/grpc-device/wiki/NI-XNET-C-Function-Reference
- 
+
 Running from command line:
 Server machine's IP address, port number, and interface name can be passed as separate command line
 arguments.

examples/nixnet/lin-signal-single-point-output.py

@@ -1,8 +1,8 @@
-r""" Write Signal Data.
- 
+r"""Write Signal Data.
+
  This example writes a signal value for 10 times.
- This is used to demonstrate a signal single point output session. 
- This example uses hardcoded signal names that use the NIXNET_exampleLDF database. 
+ This is used to demonstrate a signal single point output session.
+ This example uses hardcoded signal names that use the NIXNET_exampleLDF database.
  To use your own database, you need to add an alias to your database file using the NI-XNET
  Database Editor and then modify the database name and signals used here.
  Also ensure that the transceivers are externally powered when using C Series modules.
@@ -20,7 +20,7 @@
 
 Refer to the NI XNET gRPC Wiki for the latest C Function Reference:
   https://github.com/ni/grpc-device/wiki/NI-XNET-C-Function-Reference
- 
+
 Running from command line:
 Server machine's IP address, port number, and interface name can be passed as separate command line
 arguments.