Programmatically build Tableau packages
1 maintainer
Metadata
1 maintainer
Release files for tableau-builder 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 | |
|---|---|---|---|---|
| tableau_builder-1.0.tar.gz | 9.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tableau_builder-1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.7 kB
Release files / tableau_builder-1.0.tar.gz
| Download URL | tableau_builder-1.0.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c6a60252eb72c4e1d1b1eb7a6e007d9f4c7c18d8d971937f2775b2138e4dfd72
|
|
BLAKE2b-256 checksum How to use checksums |
451b52496253b1a0a9cf3db16e0fc980eb4d94cd6e48468cad5decdb03e3c626
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / tableau_builder-1.0-py3-none-any.whl
| Download URL | tableau_builder-1.0-py3-none-any.whl |
|---|---|
| Size | 11.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d14b08f59667ae21f118e243819cc53fb26fedb48630416d43e00295d5405f2
|
|
BLAKE2b-256 checksum How to use checksums |
a114488176705caccc08e3f7b5de3ba5ac1abc62569271ff267149f970af9816
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for tableau-builder 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.
