Closed TheChymera closed 5 months ago
given the number of similar reports -- in case of "no module" errors, please first analyze setup.{py,cfg}
for a list of dependencies to add to your gentoo packaging. Here in particular I bet we are getting fuse
module via
fsspec[fuse,http] >= 2022.1.0, != 2022.10.0
specification. Hence -- check which fuse
library fsspec depends on and add it directly as dependency
Admittedly on occasion I miss things, but yes, I always consult the python files for deps.
Both dev-python/fsspec
and sys-fs/fuse
are pulled in.
The one thing I notices while I was setting this up last week but forgot when I filed this issue, is that I noticed the flags for fsspec, which the Gentoo package does not provide.
I thought it would mean that the package just ships all features, but maybe it doesn't.
These are the packages that fsspec depends on:
The files list of the installed package shows that indeed some fuse files are installed, but maybe this is insufficient?
[deco]~ ❱ equery f fsspec | ag fuse
/usr/lib/python3.11/site-packages/fsspec/__pycache__/fuse.cpython-311.opt-1.pyc
/usr/lib/python3.11/site-packages/fsspec/__pycache__/fuse.cpython-311.opt-2.pyc
/usr/lib/python3.11/site-packages/fsspec/__pycache__/fuse.cpython-311.pyc
/usr/lib/python3.11/site-packages/fsspec/fuse.py
I guess sys-fs/fuse
is fuse library, not some python fuse bindings...
fsspec[fuse,http] >= 2022.1.0, != 2022.10.0
means that it requests fsspec
installation with optional_requires
for fuse
, which are defined in either setup.cfg
or setup.py
or pyproject.toml
. In their case apparently in the latter: https://github.com/fsspec/filesystem_spec/blob/master/pyproject.toml where they have
[project.optional-dependencies]
...
fuse = ["fusepy"]
so what you need is to add gentoo package for fusepy
.
To a degree I would consider it a bug in our packaging here since we do now import fuse
directly so we better announce it directly as well -- will do now in
Ok, I think I got confused by the required package because there are a number of packages called python and fuse:
I got the correct one, actually called fusepy now, and it works so the issue is done.
However I notice that the latest release is 6 years old and I couldn't find any test suite I could run for the package → https://github.com/fusepy/fusepy Might be worth considering regarding long-term sustainability. Seems to work (in our practical usage) with contemporary python but that might change.
I was able to get it to work via
pip install
, but for some reason, even though the tests seem to pass, the system-wide install I set up doesn't work.Some of the tests are skipped, specifically those referring to “fuse” so I assume maybe that's indicative of the issue, maybe it's somehow not linking to fuse itself? Any ideas what could be wrong?
This is the issue
But datalad wtf lists fuse:
Full build and test log → https://ppb.chymera.eu/f9fac2.html
Files installed by the extension → https://ppb.chymera.eu/fa6aca.log