bcachefs
C implementation with Python 3.7+ bindings for Bcachefs
import bcachefs as bch
# Using a filesystem-like API
with bch.mount("disk.img") as bchfs:
for root, dirs, files in bchfs.walk():
print(f"Directories in {root}: {[str(d) for d in dirs]}")
for ent in files:
with image.open(ent, "rb") as f:
for line in f.lines():
print(line)
# Using a cursor with entries cache
with bch.mount("disk.img").cd() as cursor:
for root, dirs, files in cursor.walk():
print(f"Directories in {root}: {[str(d) for d in dirs]}")
for ent in files:
with image.open(ent, "rb") as f:
for line in f.lines():
print(line)
# Using a ZipFile-like API
with Bcachefs("disk.img", "r") as image:
file_names = image.namelist()
for filename in file_names:
with image.open(filename, "rb") as f:
for line in f.lines():
print(line)
Metadata
Release files for bcachefs 0.1.16
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bcachefs-0.1.16.tar.gz | 29.7 kB | Without provenance | Details for bcachefs-0.1.16.tar.gz |
Release files / bcachefs-0.1.16.tar.gz
| Download URL | bcachefs-0.1.16.tar.gz |
|---|---|
| Size | 29.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5b01346d36e5ed900cc9d8295a9b9db313245f995d8235d92cfae52353591ffd
|
|
BLAKE2b-256 checksum How to use checksums |
2d04f57062ff85f4cb9ca54345faa55663d21aba72132abd9abdd28934fcf8d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.7.11
|
Security for bcachefs 0.1.16
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.