This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Superseded by dittolive-ditto (Ditto v5 Python SDK); this 2023 package is unmaintained.
FFI Module for Ditto.
Need a libdittoffi.so in the folder to work atm
Its path must be specified using:
export DITTOFFI_SEARCH_PATH=...
export LD_LIBRARY_PATH=...
Update Headers
When the FFI signatures change, the headers inside this directory must be updated.
dittoffi.h can be replaced by the same-titled generated file, thanks to safer-ffi.
Use make build-python at the root of the project in order to do so.
The dittoffi.cffi must be manually updated at the moment. Safer-ffi we generate it
in the future.
Need a libdittoffi.so library to work.
Metadata
Release files for dittoffi 0.0.3
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 |
|---|---|---|---|---|
| dittoffi-0.0.3.tar.gz | 32.7 kB | Without provenance | Details for dittoffi-0.0.3.tar.gz |
Release files / dittoffi-0.0.3.tar.gz
| Download URL | dittoffi-0.0.3.tar.gz |
|---|---|
| Size | 32.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c57bc1eea9803990b7d9114d67ec7f926024b65f19e7d9b8e5a5825d93acf22c
|
|
BLAKE2b-256 checksum How to use checksums |
686ff500f79ab5ffb70ed4fba07fd6c2d3f0ee10e0fa2c2bad549a77d7c07e32
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.10
|
Security for dittoffi 0.0.3
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.