A native client library for the DocRaptor HTML to PDF/XLS service. # noqa: E501
Metadata
Release files for docraptor 3.1.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 | |
|---|---|---|---|---|
| docraptor-3.1.0.tar.gz | 30.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| docraptor-3.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 119.4 kB
Release files / docraptor-3.1.0.tar.gz
| Download URL | docraptor-3.1.0.tar.gz |
|---|---|
| Size | 30.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ba6f0e8c6f1cb7eaf5c7987be4d51d09a35f95f21222d709300ddefc8dc6fa3c
|
|
BLAKE2b-256 checksum How to use checksums |
0e97b78a0527b3e93709f4cd7df614856e894a2e50d349437acb5b2256095c66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0rc3
|
Release files / docraptor-3.1.0-py3-none-any.whl
| Download URL | docraptor-3.1.0-py3-none-any.whl |
|---|---|
| Size | 89.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
044cef59c44546c15106668973168c540eefb5344532bb782540beaa6828901b
|
|
BLAKE2b-256 checksum How to use checksums |
c9d3dc74192c6de2fc41120064e21d1c26e8309d10e8327776155e7c4c219ca6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.0rc3
|
Security for docraptor 3.1.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.