datreant: persistent, pythonic trees for heterogeneous data
In many fields of science, especially those analyzing experimental or simulation data, there is often an existing ecosystem of specialized tools and file formats which new tools must work around, for better or worse. Furthermore, centralized database solutions may be suboptimal for data storage for a number of reasons, including insufficient hardware infrastructure, variety and heterogeneity of raw data, the need for data portability, etc. This is particularly the case for fields centered around simulation: simulation systems can vary widely in size, composition, rules, paramaters, and starting conditions. And with increases in computational power, it is often necessary to store intermediate results obtained from large amounts of simulation data so it can be accessed and explored interactively.
These problems make data management difficult, and serve as a barrier to answering scientific questions. To make things easier, datreant is a Python package that addresses the tedious and time-consuming logistics of intermediate data storage and retrieval. It solves a boring problem, so we can focus on interesting ones.
For more information on what datreant is and what it does, check out the official documentation.
Getting datreant
See the installation instructions for installation details. The package itself is pure Python.
If you want to work on the code, either for yourself or to contribute back to the project, clone the repository to your local machine with:
git clone https://github.com/datreant/datreant.git
Contributing
This project is still under heavy development, and there are certainly rough edges and bugs. Issues and pull requests welcome!
Check out our contributor’s guide to learn how to get started with contributing back.
Metadata
Release files for datreant 1.1.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 |
|---|---|---|---|---|
| datreant-1.1.1.tar.gz | 43.6 kB | Without provenance | Details for datreant-1.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datreant-1.1.1-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for datreant-1.1.1-py2.py3-none-any.whl |
Total release size: 91.4 kB
Release files / datreant-1.1.1.tar.gz
| Download URL | datreant-1.1.1.tar.gz |
|---|---|
| Size | 43.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da206b21c3eb713adedf0ea18f747fc9d3f9d049eebada3b2ee34f2dd8b688fb
|
|
BLAKE2b-256 checksum How to use checksums |
1657d88a239c04016845b786d0fd97dbcd9a19aa47805499a3440d490bb9639b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Release files / datreant-1.1.1-py2.py3-none-any.whl
| Download URL | datreant-1.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 47.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
6db0bd9b68c88983853308614e2c3e1a2ce162e5b20e22c397fff19e7d812c1b
|
|
BLAKE2b-256 checksum How to use checksums |
115b5be4b1cd68aefb50df937d6ea38d141f2f8f88f27440dceb4dc7c7f7f65a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.10.4
|
Security for datreant 1.1.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.