fsspec-xrootd

raw JSON →
0.5.4 verified Fri May 01 auth: no python

Provides an fsspec-compatible interface for the XRootD protocol, enabling access to remote storage systems (e.g., EOS, storage elements) via a unified filesystem-like API. Current version 0.5.4, supports Python >=3.9. Releases follow a relatively stable cadence.

pip install fsspec-xrootd

Common errors

error ModuleNotFoundError: No module named 'XRootD' ↓
cause XRootD Python bindings are missing
fix
Install XRootD: conda install xrootd or via system package manager (e.g., apt install python3-xrootd).
error FileNotFoundError: [Errno 2] No such file or directory: '/some/path' ↓
cause Path might not exist or authentication failure causes empty listing
fix
Check credentials (XROOTD_VOMS, proxy) and verify path exists. Use fs.ls('/') first to list root.
error ImportError: cannot import name 'XRootDFileSystem' from 'fsspec_xrootd' ↓
cause Typo in class name (capitalization) or outdated version (<0.5.0).
fix
Use correct capitalization: XRootDFileSystem (capital S). For older versions, check fsspec.implementations.xrootd.

Warnings

breaking In version 0.5.0, the import path changed from `fsspec_xrootd.XRootDFileSystem` to the current one. Old code using `fsspec.implementations.xrootd` still works but may break if internal refactoring occurs. ↓
fix Update imports to `from fsspec_xrootd import XRootDFileSystem`.
gotcha The XRootD Python bindings (PyPI: xrootd) are not automatically installed. Users must install them separately (e.g., via conda or system package manager). Failure to do so results in `ModuleNotFoundError: No module named 'XRootD'`. ↓
fix Install XRootD Python bindings: `conda install xrootd` or `apt install python3-xrootd` (system).
gotcha Authentication requires environment variables like `XROOTD_VOMS` or `XRDX509USERPROXY`. Without them, many operations silently fail or return empty results. ↓
fix Ensure credentials are set (e.g., `export XROOTD_VOMS=...`) before using the filesystem.

Imports