galaxy-fsspec
An fsspec filesystem that exposes a
Galaxy account as a virtual, read-only directory tree.
galaxy://
├── histories/
│ └── <history>/ (created / last_modified exposed via info())
│ ├── <dataset> (files)
│ └── <collection>/ (list, paired, list:paired, nested ...)
│ └── ... (collections nest as folders of folders)
└── libraries/
└── <library>/
├── <dataset>
└── <folder>/
└── ...
Datasets are streamed as files; collections (including nested collections) appear as directories.
Install
uv pip install galaxy-fsspec
Because the protocol is registered via the fsspec.specs entry point,
fsspec.filesystem("galaxy") and fsspec.open("galaxy://...") work without
any extra imports.
Configure
The filesystem reads two environment variables:
| Variable | Default | Purpose |
|---|---|---|
GALAXY_URL |
https://usegalaxy.org |
Galaxy server URL |
GALAXY_USER_API_KEY |
(required) | User API key |
Optional:
| Variable | Default | Purpose |
|---|---|---|
GALAXY_FSSPEC_SHOW_HID_IN_NAMES |
unset | true prefixes entries with their hid (1-my-dataset) |
You can also pass arguments explicitly:
import fsspec
fs = fsspec.filesystem("galaxy", url="https://my.galaxy.org", api_key="...", show_hid_in_names=True)
Usage
import fsspec
fs = fsspec.filesystem("galaxy")
# List histories.
for h in fs.ls("histories", detail=True):
print(h["name"])
# Timestamps (created / last_modified) are fetched lazily via info().
for h in fs.ls("histories", detail=True):
info = fs.info(h["name"])
print(info["name"], info["created"], info["last_modified"])
# Walk a history's contents — datasets are files, collections are folders.
print(fs.ls("histories/My History"))
# Read a dataset (range-aware streaming via Galaxy's display endpoint).
with fs.open("histories/My History/my-paired/forward/R1.fastq", "rb") as f:
print(f.read(64))
show_hid_in_names=True renders history entries as Galaxy does in its UI:
histories/My History/1-my-uploaded-dataset
histories/My History/30-my result
histories/My History/5-mycollection/1-forward
Scope
Read-only for now: histories, datasets, and (nested) collections. Writes, uploads, and library browsing are not yet supported.
Metadata
Release files for galaxy-fsspec 0.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| galaxy_fsspec-0.1.1.tar.gz | 134.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| galaxy_fsspec-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 149.6 kB
Release files / galaxy_fsspec-0.1.1.tar.gz
| Download URL | galaxy_fsspec-0.1.1.tar.gz |
|---|---|
| Size | 134.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
71c8da26c7a7d74d803e10447309a3ed0c4add8da9809b0d5034c14186690bc2
|
|
BLAKE2b-256 checksum How to use checksums |
57f0a3865540e89be09906459675e0d4e94d3db0b21148bd73a7eae19565bf86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / galaxy_fsspec-0.1.1-py3-none-any.whl
| Download URL | galaxy_fsspec-0.1.1-py3-none-any.whl |
|---|---|
| Size | 15.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
863f49de0ecae32dccc13acd6d601fae056cc0ef40245d6da69d5d86881e2f89
|
|
BLAKE2b-256 checksum How to use checksums |
7859cd87cf20aae0976890cce284dd99e96f3a4f594e44a1a42411ac71831916
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log