sefara
Sefara is a Python library for managing your datasets. It provides a way to specify once what your datasets are (usually fileystem paths) and any metadata (e.g. which experiment they came from), then refer to them conveniently in analysis scripts and notebooks.
Sefara doesn’t assume anything about what your datasets are, what format they’re in, or are how they are accessed.
Quick example
Define a “resource collection” by making a file like this, which we’ll call datasets.sefara.py:
from sefara import export
export(
"my_first_dataset.hdf5",
path="/path/to/file1.hdf5",
tags=["first", "important"],
)
export(
"my_second_dataset.csv",
path="/path/to/file2.csv",
tags=["second", "unimportant"],
)
Then, use Sefara to open it in Python:
>>> import sefara
>>> datasets = sefara.load("datasets.sefara.py")
>>> print(datasets.filter("tags.important")[0].path)
/path/to/file1.hdf5
Documentation
Available at: http://timodonnell.github.io/sefara/docs/html
Installation
pip install sefara
To run the tests:
nosetests
To build the documentation:
pip install -e . pip install Sphinx cd docs make clean setup rst html
The docs will be written to the _build/html directory.
Metadata
Release files for sefara 0.2.1
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 |
|---|---|---|---|---|
| sefara-0.2.1.tar.gz | 18.5 kB | Without provenance | Details for sefara-0.2.1.tar.gz |
Release files / sefara-0.2.1.tar.gz
| Download URL | sefara-0.2.1.tar.gz |
|---|---|
| Size | 18.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5d92ca3dda227c5feafd30fa265b805a0719d0e2a587a42aa6151da2f8b75677
|
|
BLAKE2b-256 checksum How to use checksums |
9eb9b680f901b08b2b55ddd70ce8941c0926fafaf405b9740ca5e49fea6582ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for sefara 0.2.1
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.