Pypeline DB is designed to simplify the creation and management of datasets. It has a friendly and easy-to-master API backed by the power of LevelDB. This allows it to manage datasets too large to fit in RAM without sacrificing data access performance.
Pypeline is great for:
Exploring data without eating all your RAM
Transforming data with maps, filters and reductions
Stopping you from losing or overwriting your data (unless you explicitly ask it to)
It’s also super easy to export a dataset from Pypeline to Pandas for further analysis.
Links
Metadata
Release files for pypeline-db 0.2.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 |
|---|---|---|---|---|
| pypeline-db-0.2.3.tar.gz | 5.3 kB | Without provenance | Details for pypeline-db-0.2.3.tar.gz |
Release files / pypeline-db-0.2.3.tar.gz
| Download URL | pypeline-db-0.2.3.tar.gz |
|---|---|
| Size | 5.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2afe470f9141c0917d26b3c104c6d3dff10ab70b7555e960b101a3ab6d9b6305
|
|
BLAKE2b-256 checksum How to use checksums |
e9b2f422baf1a7bbc9bdfdf5a1a770e838213a60d400345f8a3d1e1ffd2ac6af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pypeline-db 0.2.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.