fsspec 2023.6.0-1 source package in Ubuntu
Changelog
fsspec (2023.6.0-1) unstable; urgency=medium
* New upstream version.
* d/control: Add python3-sphinx-design as build dependency. It is needed for
build documentation package.
* d/patches/turn-off-assert-in-debian.patch: Update patch according to new
upstream release code change.
* d/rules: Ignore test_dbfs_read_range and test_dbfs_read_range_chunked
tests because they need http connections.
-- Emmanuel Arias <email address hidden> Mon, 19 Jun 2023 01:40:44 -0300
Upload details
- Uploaded by:
- Debian Python Team
- Uploaded to:
- Sid
- Original maintainer:
- Debian Python Team
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Mantic | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| fsspec_2023.6.0-1.dsc | 2.5 KiB | ecc3e753b073a2cc3a8c1d295e8c3070f7599279fba5de50c6781ce52f7020cc |
| fsspec_2023.6.0.orig.tar.gz | 377.6 KiB | 1417926a9832d82f93c7446bfcae266eade3985bf9d3f8a31917315cbd94fb72 |
| fsspec_2023.6.0-1.debian.tar.xz | 5.4 KiB | 4d14fbc041b4edf35bbbda487af31479023fc1f32a78e516993a45edc709f816 |
Available diffs
- diff from 2022.11.0-1 to 2023.6.0-1 (88.4 KiB)
No changes file available.
Binary packages built by this source
- python-fsspec-doc: specification that Python filesystems should adhere to (documentation)
The package 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.
.
This package contains the documentation.
- python3-fsspec: specification that Python filesystems should adhere to (Python 3)
The package 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.
