dash-google-charts
Google Charts components for Plotly Dash built on top of react-google-charts.
Warning: dash-google-charts is still pretty experimental, the interface and features could change, and some components may not be fully functional yet. Use with caution.
Getting started
Install with pip:
pip install dash-google-charts
See the examples for basic usage. Some examples make use of the
gviz_api helper library, available here. This is useful for
serialising your data in a JSON format ready for passing to Google Charts. The
gviz_api library can be installed with pip:
pip install gviz_api
1 maintainer
Metadata
1 maintainer
Release files for dash-google-charts 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 |
|---|---|---|---|---|
| dash-google-charts-0.0.3.tar.gz | 14.3 kB | Without provenance | Details for dash-google-charts-0.0.3.tar.gz |
Release files / dash-google-charts-0.0.3.tar.gz
| Download URL | dash-google-charts-0.0.3.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4e9b39fcb7fd3515c8b67c45984f75e48682bbbce6269996fc34458c77b9d15
|
|
BLAKE2b-256 checksum How to use checksums |
4866416f6b5596ae86bd5dae7d3fd3556f5dd741ce1e3464a8a849f935305059
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.2.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.6
|
Security for dash-google-charts 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.
