%global _empty_manifest_terminate_build 0 Name: python-fsspec Version: 2023.4.0 Release: 1 Summary: File-system specification License: BSD URL: http://github.com/fsspec/filesystem_spec Source0: https://mirrors.nju.edu.cn/pypi/web/packages/d8/c3/7eb5ace7aac24890fd6f3dbf49d547305237bd4002903f19b524061ce8ae/fsspec-2023.4.0.tar.gz BuildArch: noarch Requires: python3-adlfs Requires: python3-adlfs Requires: python3-pyarrow Requires: python3-dask Requires: python3-distributed Requires: python3-pytest Requires: python3-pytest-cov Requires: python3-dropboxdrivefs Requires: python3-requests Requires: python3-dropbox Requires: python3-adlfs Requires: python3-aiohttp Requires: python3-dask Requires: python3-distributed Requires: python3-dropbox Requires: python3-dropboxdrivefs Requires: python3-fusepy Requires: python3-gcsfs Requires: python3-libarchive-c Requires: python3-ocifs Requires: python3-panel Requires: python3-paramiko Requires: python3-pyarrow Requires: python3-pygit2 Requires: python3-requests Requires: python3-s3fs Requires: python3-smbprotocol Requires: python3-tqdm Requires: python3-fusepy Requires: python3-gcsfs Requires: python3-pygit2 Requires: python3-requests Requires: python3-gcsfs Requires: python3-panel Requires: python3-pyarrow Requires: python3-requests Requires: python3-aiohttp Requires: python3-libarchive-c Requires: python3-ocifs Requires: python3-s3fs Requires: python3-paramiko Requires: python3-smbprotocol Requires: python3-paramiko Requires: python3-tqdm %description # 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 ``` would install the base fsspec. Various optionally supported features might require specification of custom extra require, e.g. `pip install fsspec[ssh]` will install dependencies for `ssh` backends support. Use `pip install fsspec[full]` for installation of all known extra dependencies. Up-to-date package also provided through conda-forge distribution: ```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 GitHub Actions for CI. Environment files can be found in the "ci/" directory. Note that the main environment is called "py38", but it is expected that the version of python installed be adjustable at CI runtime. For local use, pick a version suitable for you. ### Testing Tests can be run in the dev environment, if activated, via ``pytest fsspec``. The full fsspec suite requires a system-level docker, docker-compose, and fuse installation. If only making changes to one backend implementation, it is not generally necessary to run all tests locally. It is expected that contributors ensure that any change to fsspec does not cause issues or regressions for either other fsspec-related packages such as gcsfs and s3fs, nor for downstream users of fsspec. The "downstream" CI run and corresponding environment file run a set of tests from the dask test suite, and very minimal tests against pandas and zarr from the test_downstream.py module in this repo. ### 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``. %package -n python3-fsspec Summary: File-system specification Provides: python-fsspec BuildRequires: python3-devel BuildRequires: python3-setuptools BuildRequires: python3-pip %description -n python3-fsspec # 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 ``` would install the base fsspec. Various optionally supported features might require specification of custom extra require, e.g. `pip install fsspec[ssh]` will install dependencies for `ssh` backends support. Use `pip install fsspec[full]` for installation of all known extra dependencies. Up-to-date package also provided through conda-forge distribution: ```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 GitHub Actions for CI. Environment files can be found in the "ci/" directory. Note that the main environment is called "py38", but it is expected that the version of python installed be adjustable at CI runtime. For local use, pick a version suitable for you. ### Testing Tests can be run in the dev environment, if activated, via ``pytest fsspec``. The full fsspec suite requires a system-level docker, docker-compose, and fuse installation. If only making changes to one backend implementation, it is not generally necessary to run all tests locally. It is expected that contributors ensure that any change to fsspec does not cause issues or regressions for either other fsspec-related packages such as gcsfs and s3fs, nor for downstream users of fsspec. The "downstream" CI run and corresponding environment file run a set of tests from the dask test suite, and very minimal tests against pandas and zarr from the test_downstream.py module in this repo. ### 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``. %package help Summary: Development documents and examples for fsspec Provides: python3-fsspec-doc %description help # 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 ``` would install the base fsspec. Various optionally supported features might require specification of custom extra require, e.g. `pip install fsspec[ssh]` will install dependencies for `ssh` backends support. Use `pip install fsspec[full]` for installation of all known extra dependencies. Up-to-date package also provided through conda-forge distribution: ```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 GitHub Actions for CI. Environment files can be found in the "ci/" directory. Note that the main environment is called "py38", but it is expected that the version of python installed be adjustable at CI runtime. For local use, pick a version suitable for you. ### Testing Tests can be run in the dev environment, if activated, via ``pytest fsspec``. The full fsspec suite requires a system-level docker, docker-compose, and fuse installation. If only making changes to one backend implementation, it is not generally necessary to run all tests locally. It is expected that contributors ensure that any change to fsspec does not cause issues or regressions for either other fsspec-related packages such as gcsfs and s3fs, nor for downstream users of fsspec. The "downstream" CI run and corresponding environment file run a set of tests from the dask test suite, and very minimal tests against pandas and zarr from the test_downstream.py module in this repo. ### 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``. %prep %autosetup -n fsspec-2023.4.0 %build %py3_build %install %py3_install install -d -m755 %{buildroot}/%{_pkgdocdir} if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi pushd %{buildroot} if [ -d usr/lib ]; then find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/lib64 ]; then find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/bin ]; then find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst fi if [ -d usr/sbin ]; then find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst fi touch doclist.lst if [ -d usr/share/man ]; then find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst fi popd mv %{buildroot}/filelist.lst . mv %{buildroot}/doclist.lst . %files -n python3-fsspec -f filelist.lst %dir %{python3_sitelib}/* %files help -f doclist.lst %{_docdir}/* %changelog * Fri Apr 21 2023 Python_Bot - 2023.4.0-1 - Package Spec generated