-
Notifications
You must be signed in to change notification settings - Fork 41
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
Parameterize get_datafile #49
Comments
As for the next release the feature freeze is already done, I will do this soon after it. Will do that more generic, so all keyword arguments can be passed down to the requests calls.
|
This will be solved in #72. |
Replaces pyDataverse DataAccessApi.get_datafile call with equivalent code that streams the response instead of fetching the entire file into memory. The StreamingDataAccessApi object can be removed once this pyDataverse issue is resolved: gdcc/pyDataverse#49 Fixes #1
As discussed during the 2024-02-14 meeting of the pyDataverse working group, we are closing old milestones in favor of a new project board at https://github.com/orgs/gdcc/projects/1 and removing issues (like this one) from those old milestones. Please feel free to join the working group! You can find us at https://py.gdcc.io and https://dataverse.zulipchat.com/#narrow/stream/377090-python |
As a developer I would like to have more control of the keyword arguments
get_datafile
uses in requests to download files. I have had issues downloading large files in the past and had to implement a customget_request
method to allow access to thestream
parameter ofrequests.get
.The text was updated successfully, but these errors were encountered: