-
Notifications
You must be signed in to change notification settings - Fork 3
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
Suggestion: flexibility regarding variable name in path #9
Comments
Whoops, didn't mean to close... Addressing this with a new development roadmap. |
@darothen I'm going to use your library and I can help with this improvement. But first of all I need to make it backward compatible with python 2.7 |
@francbartoli That's awesome! Please, feel free to contribute whatever you'd like. I do have some roadmap ideas in mind (just don't have quite enough time at the moment to deal with them), and if you'd like to chat about them over Skype or something please let me know. |
@darothen sure, I'll send you my contact privately |
For example, it could be useful to be able to handle paths like this:
{variable}/some_prefix_{param1}_{param2}_{param3}_{variable}.nc
Note: what I call {variable} should probably be called {field}.
The text was updated successfully, but these errors were encountered: