This release is a pre-release and may not be stable for production use.
Nourish is a Python API that enables data consumers and distributors to easily use and share datasets, and establishes a standard for exchanging data assets. It enables:
a data scientist to have a simpler and more unified way to begin working with a wide range of datasets, and
a data distributor to have a consistent, safe, and open source way to share datasets with interested communities.
Install the Package & its Dependencies
To install the latest version of Nourish, run
$ pip install nourish
Alternatively, if you have downloaded the source, switch to the source directory (same directory as this README file, cd /path/to/nourish-source) and run
$ pip install -U .
Quick Start
Import the package and load a dataset. Nourish will download WikiText-103 dataset (version 1.0.1) if it’s not already downloaded, and then load it.
import nourish
wikitext103_data = nourish.load_dataset('wikitext103')
View available Nourish datasets and their versions.
>>> nourish.list_all_datasets()
{'claim_sentences_search': ('1.0.2',), ..., 'wikitext103': ('1.0.1',)}
To view your globally set configs for Nourish, such as your default data directory, use nourish.get_config.
>>> nourish.get_config()
Config(DATADIR=PosixPath('dir/to/dowload/load/from'), ..., DATASET_SCHEMA_URL='file/to/load/datasets/from')
By default, nourish.load_dataset downloads to and loads from ~/.nourish/data/<dataset-name>/<dataset-version>/. To change the default data directory, use nourish.init.
nourish.init(DATADIR='new/dir/to/dowload/load/from')
Load a previously downloaded dataset using nourish.load_dataset. With the new default data dir set, Nourish now searches for the Groningen Meaning Bank dataset (version 1.0.2) in new/dir/to/dowload/load/from/gmb/1.0.2/.
gmb_data = load_dataset('gmb', version='1.0.2', download=False) # assuming GMB dataset was already downloaded
Notebooks
For a more extensive look at Nourish functionality, check out these notebooks:
Metadata
Release files for nourish 0.1a2
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 | |
|---|---|---|---|---|
| nourish-0.1a2.tar.gz | 136.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nourish-0.1a2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 179.1 kB
Release files / nourish-0.1a2.tar.gz
| Download URL | nourish-0.1a2.tar.gz |
|---|---|
| Size | 136.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8579ee9ba0e4a3a532b44de4508841c290dc0c2b241d23304473c6e403de1550
|
|
BLAKE2b-256 checksum How to use checksums |
cc3dbb9e614d4eb8d559a808df7a83c6f4c00d65b22f4428b344779d40427dd3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Release files / nourish-0.1a2-py3-none-any.whl
| Download URL | nourish-0.1a2-py3-none-any.whl |
|---|---|
| Size | 42.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2c749af520206cf9d0829e9e5eff6d0b9b69b32e77e1421e03ee5536847d5c31
|
|
BLAKE2b-256 checksum How to use checksums |
6027a258fe2c8b33223fe3321e951f8dd18ea68dcaa6c96a2b1d7620be7c7bbe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.9.2
|
Security for nourish 0.1a2
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.