Element Unify Python SDK
The Unify Python SDK is a library to interact with Element Unify. This SDK is intended for developers who are building connectors and automation software that interfaces with Element Unify.
User Information
This section is intended for users of the Unify Python SDK. This includes developers who are building connectors, integrations, and automation that interfaces with Element Unify. For developers looking to contribute to the SDK, see the Developer Information section.
Installation
You can install the Unify Python SDK from PyPI:
pip install unify-sdk
Using the Unify Python SDK with virtualenv
This assumes you have installed an appropriate version virtualenv, python, and
other associated tools. This also assumes you have an existing python project
you'd like to import into, in this case my-project.
mkdir path/to/my-project; cd path/to/my-project
virtualenv venv
source venv/bin/activate
echo unify-sdk >> requirements.txt
Then, in your python import section add the following line:
from unify.apimanager import ApiManager
Documentation
Developer guide is found in the Unify API Documentation Portal under the Unify Python SDK section.
- Navigate to your instance of Element Unify.
- Log in and select your organization.
- From the top-right menu, click on the Support icon and select API Documentation.
Asset Access
In order to use the Unify Access package, please install psycopg2-binary.
pip install psycopg2-binary
Developer Information
This section is intended for developers working to extend the Unify Python SDK.
Developer Guide
- Fork this repository.
- Revise files with your contributions.
- Follow styling guides. See Python style guide.
- Check for lint warnings. See Lint checking.
- Create a pull request with description of your changes.
Python style guide
Please use the following Python style guide Google Python Styling guide
Lint checking
We usy pylint to verify lint warnings, our build system requires a linter score of >=9.0 to pass successfully.
To locally check you changes
pip install pylint
pylint dir/to/the/file.py
Metadata
Release files for unify-sdk 4.2.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| unify-sdk-4.2.6.tar.gz | 62.0 kB | Without provenance | Details for unify-sdk-4.2.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| unify_sdk-4.2.6-py3-none-any.whl | Python 3 | none | any | Details for unify_sdk-4.2.6-py3-none-any.whl |
Total release size: 159.2 kB
Release files / unify-sdk-4.2.6.tar.gz
| Download URL | unify-sdk-4.2.6.tar.gz |
|---|---|
| Size | 62.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
309c3c8b05043a20568db04e392333c8fcf3623aaadcbce4c5cddae8fa845988
|
|
BLAKE2b-256 checksum How to use checksums |
1730753cdae598c117ce16075a309882fa61f96bda8fdcd786d3a7a1b89a4204
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.12
|
Release files / unify_sdk-4.2.6-py3-none-any.whl
| Download URL | unify_sdk-4.2.6-py3-none-any.whl |
|---|---|
| Size | 97.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bb585187b68a8a536b870d793ff4b1ee0b79cecd92ddc2b4a5331fae2e870906
|
|
BLAKE2b-256 checksum How to use checksums |
77c1075d5d1925de2d888df29d10f04c44e68e5a3f7ba8f33b89750274154b74
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.7.12
|
Security for unify-sdk 4.2.6
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.