High level DB abstraction that uses polars to represent tables in memory.
Metadata
Release files for async-db-polars 0.1.8
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 | |
|---|---|---|---|---|
| async_db_polars-0.1.8.tar.gz | 24.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| async_db_polars-0.1.8-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.5 kB
Release files / async_db_polars-0.1.8.tar.gz
| Download URL | async_db_polars-0.1.8.tar.gz |
|---|---|
| Size | 24.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3419e692c90a698c48a3a322d749112829d0424509e0d0326a73ec19e7eaa679
|
|
BLAKE2b-256 checksum How to use checksums |
6225aa03f7f78020c67730566c36b28d9493aeb11bdee8e3fc96501ef7907d99
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.4.17
|
Release files / async_db_polars-0.1.8-py3-none-any.whl
| Download URL | async_db_polars-0.1.8-py3-none-any.whl |
|---|---|
| Size | 4.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
15b52a7e6a328145da2748cd4ca694abb3aecb1723a7a24d64cf4776180ba665
|
|
BLAKE2b-256 checksum How to use checksums |
d525914d30103e7b9df4d69c69fc9a36add8227e8ec74aa9269b643226f2178e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.4.17
|
Security for async-db-polars 0.1.8
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.