-
Notifications
You must be signed in to change notification settings - Fork 125
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
api-client get_dataset_file #821
Conversation
Parameters | ||
---------- | ||
**kwargs | ||
arguments for get_dataset and download_dataset |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
arguments for get_dataset and download_dataset | |
arguments for get_dataset and download_dataset |
It is only download_dataset
right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The ones for download_dataset are explicitly separated and all the others are submitted to get_dataset.
I am a bit confused by the need of this new method. Overall, the |
There is no need for this new method. It's nothing but a shortcut for the use case of getting a particular file from the api. So far one has to do it in two steps: ds = client.get_dataset_info(...)
_, [path] = client.download_dataset(ds, ...) now it's possible in one: path = client.get_dataset_file(...) |
Good for me, just need to resolve the conflict with the changelog ;). |
…t_file # Conflicts: # CHANGELOG.md
good for merging. |
Changes proposed in this PR:
get_dataset_file
, which combines get_dataset_info and download_dataset, thus reducing boilerplate code.PR Author Checklist
develop
)PR Reviewer Checklist