-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Following latest changes I can successfully use s3 but I have errors I wouldn't know how to solve:
Instantiating filesystem MyAnaconda failed, skipping
Traceback (most recent call last):
File "~/fsspec-proxy/fsspec-proxy/env/lib/python3.12/site-packages/fsspec_proxy/file_manager.py", line 65, in initialize_filesystems
fs, url2 = fsspec.url_to_fs(fs_path, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "~/fsspec-proxy/fsspec-proxy/env/lib/python3.12/site-packages/fsspec/core.py", line 403, in url_to_fs
chain = _un_chain(url, kwargs)
^^^^^^^^^^^^^^^^^^^^^^
File "~/fsspec-proxy/fsspec-proxy/env/lib/python3.12/site-packages/fsspec/core.py", line 351, in _un_chain
cls = get_filesystem_class(protocol)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "~/fsspec-proxy/fsspec-proxy/env/lib/python3.12/site-packages/fsspec/registry.py", line 254, in get_filesystem_class
raise ValueError(f"Protocol not known: {protocol}")
ValueError: Protocol not known: anaconda
All I am trying is not working and pip install "./fsspec-proxy[anaconda]" fails with:
ERROR: Could not find a version that satisfies the requirement anaconda-cloud-storage; extra == "anaconda" (from fsspec-proxy[anaconda]) (from versions: none)
ERROR: No matching distribution found for anaconda-cloud-storage; extra == "anaconda"
I've tried to manually install it but no luck ... anyway, I am not blocked by this issue but it's a bit unexpected to read all those failures for a variant of the proxy that wouldn't use anacoinda at all
Metadata
Metadata
Assignees
Labels
No labels