File-system specification
Project description
filesystem_spec
A specification for pythonic filesystems.
Install
pip install fsspec
or
conda install -c conda-forge fsspec
Purpose
To produce a template or specification for a file-system interface, that specific implementations should follow,
so that applications making use of them can rely on a common behaviour and not have to worry about the specific
internal implementation decisions with any given backend. Many such implementations are included in this package,
or in sister projects such as s3fs and gcsfs.
In addition, if this is well-designed, then additional functionality, such as a key-value store or FUSE mounting of the file-system implementation may be available for all implementations "for free".
Documentation
Please refer to RTD
Develop
fsspec uses tox and
tox-conda to manage dev and test
environments. First, install conda with tox and tox-conda in a base environment
(eg. conda install -c conda-forge tox tox-conda). Calls to tox can then be
used to configure a development environment and run tests.
First, setup a development conda environment via tox -e dev. This will
install fspec dependencies, test & dev tools, and install fsspec in develop
mode. Then, activate the dev environment under .tox/dev via conda activate .tox/dev.
Testing
Tests can be run directly in the activated dev environment via pytest fsspec.
The full fsspec test suite can be run via tox, which will setup and execute
tests against multiple dependency versions in isolated environment. Run tox -av to list available test environments, select environments via tox -e <env>.
The full fsspec suite requires a system-level docker, docker-compose, and fuse
installation. See ci/install.sh for a detailed installation example.
Code Formatting
fsspec uses Black to ensure
a consistent code format throughout the project. black is automatically
installed in the tox dev env, activated via conda activate .tox/dev.
Then, run black fsspec from the root of the filesystem_spec repository to
auto-format your code. Additionally, many editors have plugins that will apply
black as you edit files.
Optionally, you may wish to setup pre-commit hooks to
automatically run black when you make a git commit. black is automatically
installed in the tox dev env, activated via conda activate .tox/dev.
Then, run pre-commit install --install-hooks from the root of the
filesystem_spec repository to setup pre-commit hooks. black will now be run
before you commit, reformatting any changed files. You can format without
committing via pre-commit run or skip these checks with git commit --no-verify.
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
File details
Details for the file fsspec-0.5.2.tar.gz.
File metadata
- Download URL: fsspec-0.5.2.tar.gz
- Upload date:
- Size: 64.2 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/3.7.3
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 | 6531a5fa9ea6bf27a5180d225558a8a7aa5d7c3cbf7e8b146dd37ac699017937 |
|
| MD5 | f6d7dfae9e25b501098ed41af14be839 |
|
| BLAKE2b-256 | 541859f1850336568168144a746afa7199a0311f1a89bdb7b0d8e8b50d2c3d93 |
