A previous release had provenance metadata, but this release does not. View details.
PolyStore
Framework-agnostic storage primitives for scientific applications.
PolyStore owns backend interfaces, execution-local backend registries,
FileManager routing, storage formats, ROI values, virtual-workspace source
references, and viewer-streaming payload mechanics. Applications retain
ownership of domain artifact names and materialization policy.
Quick start
Pass an explicit mapping of backend names to instances. FileManager has no
global fallback and does not infer a backend from a path.
from pathlib import Path
import numpy as np
from polystore import DiskBackend, FileManager, MemoryBackend
registry = {
"disk": DiskBackend(),
"memory": MemoryBackend(),
}
files = FileManager(registry)
data = np.arange(6).reshape(2, 3)
files.save(data, Path("output.npy"), backend="disk")
loaded = files.load(Path("output.npy"), backend="disk")
For application startup where every discoverable context-free backend is wanted, use the package-owned lazy registry:
from polystore import FileManager, ensure_storage_registry, storage_registry
ensure_storage_registry()
files = FileManager(dict(storage_registry))
Backends requiring context-specific construction, including virtual workspaces and OMERO, must be instantiated by the application and added to its registry.
Nominal backend extension
Concrete backends inherit DataSource, DataSink, StorageBackend, or
ReadOnlyBackend and declare their backend key. The authoritative class
catalog is BackendBase.__registry__ (also exported as
STORAGE_BACKENDS). Do not build a second backend class table.
Installation
python -m pip install polystore
The core install includes NumPy, ArrayBridge, metaclass-registry, file locking,
platform-aware cache paths, image I/O, Zarr/OME-Zarr support, and ZMQRuntime.
Framework and streaming extras add their corresponding optional runtimes.
Install polystore[bioformats] for the package-owned PyImageJ and
Bio-Formats bridge. Its first use materializes a checksummed Fiji, JDK, and
PyImageJ bridge runtime; later processes reuse that complete local cache
without Maven resolution.
Full documentation: polystore.readthedocs.io
Metadata
Release files for polystore 0.6.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| polystore-0.6.3.tar.gz | 194.8 kB | Without provenance | Details for polystore-0.6.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| polystore-0.6.3-py3-none-any.whl | Python 3 | none | any | Details for polystore-0.6.3-py3-none-any.whl |
Total release size: 348.7 kB
Release files / polystore-0.6.3.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | polystore-0.6.3.tar.gz |
|---|---|
| Size | 194.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fc87bef43b56e010519d02cb2a4fb44cc307860808f3ed053714d5f49434ed35
|
|
BLAKE2b-256 checksum How to use checksums |
b9f3569196ee6d18f5441e22080ac8d7813dd593dc337e9f371246de5381e080
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Release files / polystore-0.6.3-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | polystore-0.6.3-py3-none-any.whl |
|---|---|
| Size | 153.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5e695acd9d105d30226c8df9ea0873b177d83ffb258e290b88f8ee3358617b96
|
|
BLAKE2b-256 checksum How to use checksums |
cb373294d1b666a200334e61d010f3370477637c2cb09fe52d55500d4859ea1c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.14
|
Security for polystore 0.6.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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.6.0 2 files With provenance
- Added 0.6.3 2 files Without provenance
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.