python bindings for liner.
Metadata
Release files for liner-py 1.0.2357
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| liner_py-1.0.2357-cp32-abi3-win_arm64.whl | CPython 3.2 | abi3 | Windows ARM64 | Details |
| liner_py-1.0.2357-cp32-abi3-win_amd64.whl | CPython 3.2 | abi3 | Windows x86-64 | Details |
| liner_py-1.0.2357-cp32-abi3-manylinux_2_34_x86_64.whl | CPython 3.2 | abi3 | Linux glibc 2.34+ x86-64 | Details |
| liner_py-1.0.2357-cp32-abi3-manylinux_2_34_aarch64.whl | CPython 3.2 | abi3 | Linux glibc 2.34+ ARM64 | Details |
| liner_py-1.0.2357-cp32-abi3-macosx_11_0_x86_64.whl | CPython 3.2 | abi3 | macOS 11.0+ x86-64 | Details |
Total release size: 56.2 MB
Release files / liner_py-1.0.2357-cp32-abi3-win_arm64.whl
| Download URL | liner_py-1.0.2357-cp32-abi3-win_arm64.whl |
|---|---|
| Size | 9.8 MB |
| Tags | CPython 3.2 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
56ffdee4433f3fdcb3332b6e39bd56f23c4a4d2418f4e154c583fbd3ef5bf951
|
|
BLAKE2b-256 checksum How to use checksums |
0afa43c3383afc01c79e72af207059a26fe311a31c188dc2f9cbab6729274ac1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / liner_py-1.0.2357-cp32-abi3-win_amd64.whl
| Download URL | liner_py-1.0.2357-cp32-abi3-win_amd64.whl |
|---|---|
| Size | 10.9 MB |
| Tags | CPython 3.2 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
c9f5257cf3c536ec3588c2a6f53bc396f53965cff93f3b01606a394d89524d93
|
|
BLAKE2b-256 checksum How to use checksums |
a4156a090574937d18b41803f412d0a665185ac736dd395e68af36d576057192
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / liner_py-1.0.2357-cp32-abi3-manylinux_2_34_x86_64.whl
| Download URL | liner_py-1.0.2357-cp32-abi3-manylinux_2_34_x86_64.whl |
|---|---|
| Size | 12.9 MB |
| Tags | CPython 3.2 Linux glibc 2.34+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
86d164c1252c8e3bf9a4c42720d9827acaa52e7357b396d077fb45834ac29eaa
|
|
BLAKE2b-256 checksum How to use checksums |
5739d47fc54a9a9c88d0227f53a8d6cf6ba3fe3bb133e02ca3fd44bd8e20192e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.3
|
Release files / liner_py-1.0.2357-cp32-abi3-manylinux_2_34_aarch64.whl
| Download URL | liner_py-1.0.2357-cp32-abi3-manylinux_2_34_aarch64.whl |
|---|---|
| Size | 11.9 MB |
| Tags | CPython 3.2 Linux glibc 2.34+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
035a15e279cd367125689298db3e762ef24bdcd8c489937076a0694969eaada9
|
|
BLAKE2b-256 checksum How to use checksums |
7971c7f6dea639c615f4ac1cb848872a3d697dde77a3556957494b56d32be998
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.10.12
|
Release files / liner_py-1.0.2357-cp32-abi3-macosx_11_0_x86_64.whl
| Download URL | liner_py-1.0.2357-cp32-abi3-macosx_11_0_x86_64.whl |
|---|---|
| Size | 10.7 MB |
| Tags | CPython 3.2 abi3 macOS 11.0+ x86-64 |
|
SHA-256 checksum How to use checksums |
2f39fb214d0df7eaf1433bce61e47bb2e33bb754daeb9b4d2b6e9e6f4f812591
|
|
BLAKE2b-256 checksum How to use checksums |
bcff7ec821559a9b8fc135ac349c621a447b7150d97a6c36f2eb69f61e2e5659
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for liner-py 1.0.2357
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.