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

Catch file type (netCDF3, netCDF-classic, etc) roadbloacks before any module has to deal with it #40

Open
valeriupredoi opened this issue Nov 4, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@valeriupredoi
Copy link
Collaborator

Right now we have catches for these immediately before any operation may fail (ie if file doesn't exist right before calling active on it, if file is netCDF3/classic right before kerchunking/h5py-ing it etc)- we should be able to do this cleaner and more open to the user/API before anything gets piped through - as @bnlawrence mentions at the point where we call netCDF.Dataset for the very first time?

@valeriupredoi valeriupredoi added the enhancement New feature or request label Nov 4, 2022
@valeriupredoi valeriupredoi self-assigned this Nov 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant