Default cache for open_local?

Open
#438 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start at the open_local entry point and inspect how local and caching filesystems are handled, including the simplecache and temporary-storage path. Done means unsupported filesystems return a usable local path through simplecache instead of raising, while existing supported cases continue to work.

Written by the indexing model from the issue text.

Description

Currently, open_local can only be called with the local filesystem, or one of the cacheing ones (because it returns a local path, by design). It you give anything else, you get an error. Instead, we could fall back to using simplecache (and temporary storage) for cases where we would have errored.

Dominant language
Python
Stars
1.4k
Forks
490
Avg merge
2d 3h
Merged PRs (30d)
38

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fsspec/filesystem_spec

All issues in fsspec/filesystem_spec

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.