Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translate time metadata from GCS names to fsspec standard names. #563

Merged
merged 3 commits into from
Jun 27, 2023
Merged

Conversation

cvm-a
Copy link
Contributor

@cvm-a cvm-a commented Jun 26, 2023

To fix issue #559.

@martindurant
Copy link
Member

Thank you, looks good!
Any chance of adding a test to ensure we don't loose this behaviour in the future?

@cvm-a
Copy link
Contributor Author

cvm-a commented Jun 27, 2023

Thank you, looks good! Any chance of adding a test to ensure we don't loose this behaviour in the future?

The added lines in test_core.py should fail if the two new fields are not present. Is there anything else we should test for?

Also, should we remove the old GCS-specific names? It doesn't seem to be a documented part of the API, but I don't know what is your policy if someone is depending on them despite that (Hyrum's law).

@martindurant
Copy link
Member

Also, should we remove the old GCS-specific names?

I'd say it's fine to keep the original names too

@martindurant martindurant merged commit 23fc756 into fsspec:main Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants