This package provides the core libraries used for build a dashboard server like known from dashing. See xdashboard for a sample dashboard server implementation.
CHANGES
0.5.2 (2017-01-24)
bugfix: check existence of _scheduler before calling stop on them
switch default maintainAspectRatio to false for ChartJS widget
cleanup ISampler interfaces, remove _enqueue method from interface. It’s up to the developer hwo to implement the enqueue concept
update MANIFEST.in, used check-manifest for define include pattern
0.5.1 (2017-01-07)
feature: added Rickshaw graph widget. You can use this widget with data-type=”Graph”
feature: added stream data to global stream collection. This will ensure, that the widgets get initial data and doesn’t have to wait till the first timout expires
0.5.0 (2017-01-05)
initial release
Metadata
Release files for p01.dashboard 0.5.2
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 |
|---|---|---|---|---|
| p01.dashboard-0.5.2.tar.gz | 1.6 MB | Without provenance | Details for p01.dashboard-0.5.2.tar.gz |
Release files / p01.dashboard-0.5.2.tar.gz
| Download URL | p01.dashboard-0.5.2.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
af77eea5449a64353882c662eac34ab9b7ad59a9f28145539c69d2770d7820c7
|
|
BLAKE2b-256 checksum How to use checksums |
9c7aed95fc5ff1313ee46a8d1caf961c97a51c9c06e30e2b262ba3bd9a1165f3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for p01.dashboard 0.5.2
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.