This project is a python wrapper for the API for Dolibarr ERP & CRM found at dolibarr.org. It is not yet complete, but most major GET endpoints has been implemented. In the beginning I will mostly focus on implementing the API endpoints that I use.
1 maintainer
Metadata
1 maintainer
Release files for dolibarrpy 0.11.0
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 | |
|---|---|---|---|---|
| dolibarrpy-0.11.0.tar.gz | 16.8 kB | Without provenance | Details |
Release files / dolibarrpy-0.11.0.tar.gz
| Download URL | dolibarrpy-0.11.0.tar.gz |
|---|---|
| Size | 16.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e7f9315f2b50e6e083346437b37be9ae1014bba7c251d88591335c5c2d196e83
|
|
BLAKE2b-256 checksum How to use checksums |
cb0a368a855c5c4d58a460a369e2ea0594e0f31bc5f105517790003bfbdd1cdd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for dolibarrpy 0.11.0
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.
