Info |
NI FlexLogger API for Python |
Author |
NI |
About
The niflexlogger-automation package contains an API (Application Programming Interface) and examples for using Python to automate FlexLogger. The automation API supports modifying the configuration of existing FlexLogger projects and controlling the execution of FlexLogger tests. The package is implemented in Python. NI created and supports this package.
Requirements
niflexlogger-automation has the following requirements:
FlexLogger 2024 Q1+
CPython 3.6 - 3.13. If you do not have Python installed on your computer, go to python.org/downloads to download and install it.
Installation
To install niflexlogger-automation, use one of the following methods:
pip:
$ python -m pip install niflexlogger-automation
easy_install from setuptools:
$ python -m easy_install niflexlogger-automation
Download the project source and run:
$ python setup.py install
Using the FlexLogger Python API
Refer to the documentation for detailed information on how to use niflexlogger-automation.
Refer to Getting Started with CompactDAQ and FlexLogger, for more information on installing FlexLogger, using hardware, or downloading FlexLogger examples.
Contribution to the FlexLogger Python API
If you would like to contribute to this API, first validate your changes using the provided automated tests. The Python API package contains a number of automated tests which should be used to validate API changes before submitting a pull request. If a pull request contains new API functionality, new automated tests that exercise the new functionality should be included with the pull request.
To run the automated tests for the Python API, you must first configure FlexLogger to load the test plugins that the test projects use. To do this, copy tests/assets/pythonTests.config to %public%\Documents\National Instruments\FlexLogger\Plugins\IOPlugins, and in that file replace <path to git repo> with the path to the cloned repo.
After this is done, you can run the tests with tox.
Support / Feedback
The niflexlogger-automation package is supported by NI. For support for niflexlogger-automation, open a request through the NI support portal at ni.com.
Bugs / Feature requests
To report a bug or submit a feature request, use the GitHub issues page.
License
niflexlogger-automation is licensed under an MIT-style license (see LICENSE). Other incorporated projects may be licensed under different licenses. All licenses allow for non-commercial and commercial use.
Metadata
Release files for niflexlogger-automation 0.2.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| niflexlogger_automation-0.2.4-py3-none-any.whl | Python 3 | none | any | Details |
Release files / niflexlogger_automation-0.2.4-py3-none-any.whl
| Download URL | niflexlogger_automation-0.2.4-py3-none-any.whl |
|---|---|
| Size | 81.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ebc4a5364d0ebdb2fadcbe11085e72892273094dd59cb95bbd8c7fa6527302a
|
|
BLAKE2b-256 checksum How to use checksums |
7ae1572037a5bbc3bf9bb12301bb043a8555f2994cafcc169ff9710ce9e6d74a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for niflexlogger-automation 0.2.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.