The PhilDB timeseries database client aims to provide a PhilDB database API compatible object. At this stage mostly the read related methods have been implemented. None of the write related methods have been implemented. Any methods yet to be implemented in the client will raise a NotImplementedError if called.
Example usage
from phildb_client import PhilDBClient
db = PhilDBClient('http://localhost:8889')
db.ts_list()Notes
This client is experimental and depends on the experimental PhilDB server. By default the client reads data from the server in the msgpack format. The data served by the server and read by the client is using the experimental Pandas msgpack implementation, as such it is dependant on the version of Pandas used by the server and the client being compatible. There is a known issue with Pandas < v0.17 (which has been made a dependency for the server), the client however can use an older version of Pandas and use JSON as the transport format instead of msgpack if required. For example: .. code:
from phildb_client import PhilDBClient
db = PhilDBClient('http://localhost:8889', 'json')
1 maintainer
Metadata
1 maintainer
Release files for phildb-client 0.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 | Actions |
|---|---|---|---|---|
| phildb-client-0.1.0.tar.gz | 19.8 kB | Without provenance | Details for phildb-client-0.1.0.tar.gz |
Release files / phildb-client-0.1.0.tar.gz
| Download URL | phildb-client-0.1.0.tar.gz |
|---|---|
| Size | 19.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
616789c7c71316dd81fefc8a01ecf074e65b148427e96f0250e2957cde10cf73
|
|
BLAKE2b-256 checksum How to use checksums |
86fb3a670119eafd9d041813c9ecfd1fc2b56c9134e0690597127ac476364608
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for phildb-client 0.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
