MeT IOT Communication
Useful Links
Changelog v0.1.7 - v0.1.8 - v0.1.9
- Add automated builds for newer python builds
Known issues
- Exit Signal (SIGABRT/SIGSEGV): Upon exiting the Python interpreter, a
free(): invalid pointererror may occur.- Reason: This is a known teardown conflict between the Python Garbage Collector and the C++ Runtime (libstdc++). It occurs after all user code has executed.
- Impact: None. This does not affect data transmission or device logic during the program's lifecycle.
How To Use
Importing the Library
Use pip to install the library
pip install MeTIOT
Programming with the Library
Testing the library imported successfully
You can use this code to test you can successfully import the library into your code.
import MeTIOT
client = MeTIOT.DeviceClient("0.0.0.0", 12345)
print(type(client))
print("MeTIOT import successful!")
Using the library
For further information on how to use this library refer to the PYTHON_LIB_GUIDE.md document.
How to compile and use from this repository
Linux based systems:
- Clone the repository
git clone https://github.com/Microelectronic-Technologies/MeTIOTCommunication.git
- Navigate into repository
cd MeTIOTCommunication/
- Create and navigate into build directory
mkdir build
cd build
- Compile library using CMake
cmake ..
cmake --build . --config Release
- Export path to python
export PYTHONPATH=./src/python_bindings:$PYTHONPATH
- Now you can use and import the library in your current directory
- (optional) Test the library is python
python3
import MeTIOT
client = MeTIOT.DeviceClient("0.0.0.0", 12345)
type(client)
1 maintainer
Metadata
1 maintainer
Release files for MeTIOT 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
Total release size: 7.8 MB
Release files / metiot-0.1.10-cp314-cp314-musllinux_1_2_x86_64.whl
| Download URL | metiot-0.1.10-cp314-cp314-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.14 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
b7edd62f2c217f5cb853bfd8d8c9e54de5b99fd8c6512ca3b225e7c7f643a419
|
|
BLAKE2b-256 checksum How to use checksums |
0a5b6ce4ab2db6f7d4f7fd78e81041cacb9b3bc7cb06001af2c7d30075119d86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp314-cp314-musllinux_1_2_aarch64.whl
| Download URL | metiot-0.1.10-cp314-cp314-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.14 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
5a82bc3292b4926a2d82dee7bf7cf4b054f22dbb58c8e81f76a92d8cc62c7197
|
|
BLAKE2b-256 checksum How to use checksums |
4abfc565288fe1120e3ec7857498355f43a148271c808fccd3997632fe97686f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp314-cp314-manylinux_2_34_x86_64.whl
| Download URL | metiot-0.1.10-cp314-cp314-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 152.2 kB |
| Tags | CPython 3.14 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
a94eeb9f08e7e3e6f8bff92594f441863167bf3d6221e33b269ee9f9ed49cfb5
|
|
BLAKE2b-256 checksum How to use checksums |
1035bc011879c66dc2c5ce9d0bdbd07a84c195154d35db388439c7c5daa8a246
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp314-cp314-manylinux_2_34_aarch64.whl
| Download URL | metiot-0.1.10-cp314-cp314-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 136.4 kB |
| Tags | CPython 3.14 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
2423cc76f9f950ba510695e2a23cf3760fd045796cbdf4faef373fa819c2bc99
|
|
BLAKE2b-256 checksum How to use checksums |
2ee1d5390ff84f05c96d8ca8186be5775b3fa3053212c13907a4354050436c19
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp313-cp313-musllinux_1_2_x86_64.whl
| Download URL | metiot-0.1.10-cp313-cp313-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.13 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
976b300321638e59025e18036ffb0b901f4ca76077b7fda58f3041b32c6a2960
|
|
BLAKE2b-256 checksum How to use checksums |
02a227be71fc2ccd9adf13a596e5c94d999c67821f31267294f3513525099d51
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp313-cp313-musllinux_1_2_aarch64.whl
| Download URL | metiot-0.1.10-cp313-cp313-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.13 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
e3ce4deca48955634ccbcac492bbd3f3531efdbe144021a07c014e50f4d47f82
|
|
BLAKE2b-256 checksum How to use checksums |
f40c743e24d5dc7f8b66050ab1e3eafd58813a0440441492c226043f5aa9cca4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp313-cp313-manylinux_2_34_x86_64.whl
| Download URL | metiot-0.1.10-cp313-cp313-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 152.1 kB |
| Tags | CPython 3.13 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
9dedd0d393c9a247118ec641c8a39d90b2e6b6a2a5a1711c4d168d729e5fd20c
|
|
BLAKE2b-256 checksum How to use checksums |
c4955d15011d3210afac1642e9af4baa67897111687d779e9e43e134a280a231
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp313-cp313-manylinux_2_34_aarch64.whl
| Download URL | metiot-0.1.10-cp313-cp313-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 135.6 kB |
| Tags | CPython 3.13 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
54f4f017f741b01500227473d87783a62a4bc66646fe553287099953a10aaacb
|
|
BLAKE2b-256 checksum How to use checksums |
9db083642f6afcb1b4e4f7cab2dbb4b2035b0f913b5dec9bb8429011b449d53d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp312-cp312-musllinux_1_2_x86_64.whl
| Download URL | metiot-0.1.10-cp312-cp312-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 1.2 MB |
| Tags | CPython 3.12 Linux musl 1.2+ x86-64 |
|
SHA-256 checksum How to use checksums |
bf4e4b895a5dbf38cae801709398d11de3a900850a3dd266ae9b2104098d1c53
|
|
BLAKE2b-256 checksum How to use checksums |
70e5caf1795fb35556aaa91e104624d38a5740a029de9d85a653b0eb644ec8b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp312-cp312-musllinux_1_2_aarch64.whl
| Download URL | metiot-0.1.10-cp312-cp312-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 1.1 MB |
| Tags | CPython 3.12 Linux musl 1.2+ ARM64 |
|
SHA-256 checksum How to use checksums |
dea8c4498dc1f24a20e18f9761569e59b04648ca009edf76635e161f5fbe19fd
|
|
BLAKE2b-256 checksum How to use checksums |
b01f7bba89adfc8ee779e5bc9d98ea66120d7889dffc651c16cfb5fba512d733
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp312-cp312-manylinux_2_34_x86_64.whl
| Download URL | metiot-0.1.10-cp312-cp312-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 151.9 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ x86-64 |
|
SHA-256 checksum How to use checksums |
afd0479377443689b8e8a07f31a0d0f8146ba3b838f52e4d755603ed60ee1d9b
|
|
BLAKE2b-256 checksum How to use checksums |
7aa2dbf63e2dda60b418dbca42365bb992a8bbd35c3647323206b801996e08f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / metiot-0.1.10-cp312-cp312-manylinux_2_34_aarch64.whl
| Download URL | metiot-0.1.10-cp312-cp312-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 134.6 kB |
| Tags | CPython 3.12 Linux glibc 2.34+ ARM64 |
|
SHA-256 checksum How to use checksums |
c2e8100aba2d1a34e416c6d0892e8dfd3c76ee90ec18034b39a189b1efe61e87
|
|
BLAKE2b-256 checksum How to use checksums |
5ca7e2b22ff8a566c6ae1921acbb8c46d040f8e752b99f941934ce27274db6a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for MeTIOT 0.1.10
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.
Full provenance
All 12 files in this release have been uploaded with provenance metadata.
Attestation for metiot-0.1.10-cp314-cp314-musllinux_1_2_x86_64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA 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.
