FM / fsspec-2022.1.0.dist-info

/usr/local/lib/python3.6/site-packages/fsspec-2022.1.0.dist-info/

/usr/local/lib/python3.6/site-packages/fsspec-2022.1.0.dist-info

Name	Size	Mode	Actions
INSTALLER	4	0644	edit dl rm
LICENSE	1513	0644	edit dl rm
METADATA	5368	0644	edit dl rm
RECORD	6011	0644	edit dl rm
top_level.txt	7	0644	edit dl rm
WHEEL	92	0644	edit dl rm

Edit: /usr/local/lib/python3.6/site-packages/fsspec-2022.1.0.dist-info/METADATA (5368B)

# filesystem_spec

[![PyPI version](https://badge.fury.io/py/fsspec.svg)](https://pypi.python.org/pypi/fsspec/)
[![Anaconda-Server Badge](https://anaconda.org/conda-forge/fsspec/badges/version.svg)](https://anaconda.org/conda-forge/fsspec)
![Build](https://github.com/fsspec/filesystem_spec/workflows/CI/badge.svg)
[![Docs](https://readthedocs.org/projects/filesystem-spec/badge/?version=latest)](https://filesystem-spec.readthedocs.io/en/latest/?badge=latest)

A specification for pythonic filesystems.

## Install

```bash
pip install fsspec
```
or
```bash
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](https://filesystem-spec.readthedocs.io/en/latest/?badge=latest)

## Develop

fsspec uses [tox](https://tox.readthedocs.io/en/latest/) and
[tox-conda](https://github.com/tox-dev/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 {env}`` where ``env`` is one of ``{py36,py37,py38,py39}``.
This will install fspec dependencies, test & dev tools, and install fsspec in develop
mode. You may activate the dev environment under ``.tox/{env}`` via ``conda activate .tox/{env}``.

### Testing

Tests can be run in the dev environment, if activated, via ``pytest fsspec``.

Alternatively, the full fsspec test suite can also be run via ``tox``, which will
also build the appropriate environment (see above), with the environment specified
by the TOXENV environment variable.

The full fsspec suite requires a system-level docker, docker-compose, and fuse
installation.

### Code Formatting

fsspec uses [Black](https://black.readthedocs.io/en/stable) to ensure
a consistent code format throughout the project.
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. ``black`` is included in the ``tox`` environments.

Optionally, you may wish to setup [pre-commit hooks](https://pre-commit.com) to
automatically run ``black`` when you make a git commit.
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``.

Metadata-Version: 2.1 Name: fsspec Version: 2022.1.0 Summary: File-system specification Home-page: http://github.com/fsspec/filesystem_spec Maintainer: Martin Durant Maintainer-email: mdurant@anaconda.com License: BSD Keywords: file Platform: UNKNOWN Classifier: Development Status :: 4 - Beta Classifier: Intended Audience :: Developers Classifier: License :: OSI Approved :: BSD License Classifier: Operating System :: OS Independent Classifier: Programming Language :: Python :: 3.6 Classifier: Programming Language :: Python :: 3.7 Classifier: Programming Language :: Python :: 3.8 Classifier: Programming Language :: Python :: 3.9 Requires-Python: >=3.6 Description-Content-Type: text/markdown Provides-Extra: abfs Requires-Dist: adlfs ; extra == 'abfs' Provides-Extra: adl Requires-Dist: adlfs ; extra == 'adl' Provides-Extra: arrow Requires-Dist: pyarrow (>=1) ; extra == 'arrow' Provides-Extra: dask Requires-Dist: dask ; extra == 'dask' Requires-Dist: distributed ; extra == 'dask' Provides-Extra: dropbox Requires-Dist: dropboxdrivefs ; extra == 'dropbox' Requires-Dist: requests ; extra == 'dropbox' Requires-Dist: dropbox ; extra == 'dropbox' Provides-Extra: entrypoints Requires-Dist: importlib-metadata ; (python_version < "3.8") and extra == 'entrypoints' Provides-Extra: fuse Requires-Dist: fusepy ; extra == 'fuse' Provides-Extra: gcs Requires-Dist: gcsfs ; extra == 'gcs' Provides-Extra: git Requires-Dist: pygit2 ; extra == 'git' Provides-Extra: github Requires-Dist: requests ; extra == 'github' Provides-Extra: gs Requires-Dist: gcsfs ; extra == 'gs' Provides-Extra: gui Requires-Dist: panel ; extra == 'gui' Provides-Extra: hdfs Requires-Dist: pyarrow (>=1) ; extra == 'hdfs' Provides-Extra: http Requires-Dist: requests ; extra == 'http' Requires-Dist: aiohttp ; extra == 'http' Provides-Extra: libarchive Requires-Dist: libarchive-c ; extra == 'libarchive' Provides-Extra: oci Requires-Dist: ocifs ; extra == 'oci' Provides-Extra: s3 Requires-Dist: s3fs ; extra == 's3' Provides-Extra: sftp Requires-Dist: paramiko ; extra == 'sftp' Provides-Extra: smb Requires-Dist: smbprotocol ; extra == 'smb' Provides-Extra: ssh Requires-Dist: paramiko ; extra == 'ssh' # filesystem_spec [![PyPI version](https://badge.fury.io/py/fsspec.svg)](https://pypi.python.org/pypi/fsspec/) [![Anaconda-Server Badge](https://anaconda.org/conda-forge/fsspec/badges/version.svg)](https://anaconda.org/conda-forge/fsspec) ![Build](https://github.com/fsspec/filesystem_spec/workflows/CI/badge.svg) [![Docs](https://readthedocs.org/projects/filesystem-spec/badge/?version=latest)](https://filesystem-spec.readthedocs.io/en/latest/?badge=latest) A specification for pythonic filesystems. ## Install ```bash pip install fsspec ``` or ```bash 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](https://filesystem-spec.readthedocs.io/en/latest/?badge=latest) ## Develop fsspec uses [tox](https://tox.readthedocs.io/en/latest/) and [tox-conda](https://github.com/tox-dev/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 {env}`` where ``env`` is one of ``{py36,py37,py38,py39}``. This will install fspec dependencies, test & dev tools, and install fsspec in develop mode. You may activate the dev environment under ``.tox/{env}`` via ``conda activate .tox/{env}``. ### Testing Tests can be run in the dev environment, if activated, via ``pytest fsspec``. Alternatively, the full fsspec test suite can also be run via ``tox``, which will also build the appropriate environment (see above), with the environment specified by the TOXENV environment variable. The full fsspec suite requires a system-level docker, docker-compose, and fuse installation. ### Code Formatting fsspec uses [Black](https://black.readthedocs.io/en/stable) to ensure a consistent code format throughout the project. 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. ``black`` is included in the ``tox`` environments. Optionally, you may wish to setup [pre-commit hooks](https://pre-commit.com) to automatically run ``black`` when you make a git commit. 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``.