fsspec 2024.3.1-1 source package in Ubuntu
Changelog
fsspec (2024.3.1-1) unstable; urgency=medium
* New upstream version
* Standards-Version: 4.7.0 (routine-update)
* d/patches/turn-off-assert-in-debian.patch: Remove patch that is not longer
needed. Also, update 0002-Remove-privacy-breach-in-documentation.patch
patch according to the new upstream release code.
* d/tests/fsspec-tests: force symbolic link creation in autopkgtest.
-- Emmanuel Arias <email address hidden> Sun, 21 Apr 2024 20:47:01 -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 | |
|---|---|---|---|---|
| Oracular | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| fsspec_2024.3.1-1.dsc | 2.5 KiB | f6a1ae268275f8be66f1f40cbb33ceefa8e74cb04e08b2171c8645a8534f6d4a |
| fsspec_2024.3.1.orig.tar.gz | 416.7 KiB | 5c5040762cf644762a5777444cd1302dbd0ea7e88cb3d8645164398e8762ec3a |
| fsspec_2024.3.1-1.debian.tar.xz | 6.6 KiB | e8834f6b28ca5141f6e5ef550098bbd923b079b38de5562f516bc9d982c28671 |
Available diffs
- diff from 2024.2.0-1 to 2024.3.1-1 (15.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.
