fsspec / fsspec/filesystem_spec
Add ctime/mtime to list of expected values in info
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 490
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 38
Description
Created and/or modified time is returned in the file info of most backends. We should endeavour to surface these in the file info dict with a common format (datetime.datetime? unix timestamp?) and key names.
e.g.,
--- a/fsspec/implementations/local.py
+++ b/fsspec/implementations/local.py
@@ -78,6 +78,8 @@ class LocalFileSystem(AbstractFileSystem):
result["size"] = out2.st_size
except IOError:
result["size"] = 0
+ result['created'] = datetime.datetime.utcfromtimestamp(result["created"])
+ result['modified'] = datetime.datetime.utcfromtimestamp(result["mtime"])
return result
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the file-info handling in fsspec/implementations/local.py and comparing the metadata returned by other backends. Resolve the common key names and representation for created and modified times before making changes. Done means the file info dict exposes these values consistently across the relevant backends.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100