-
Notifications
You must be signed in to change notification settings - Fork 52
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
[FEATURE] - Provide Ability to Write Downloaded Data to a File #567
Comments
Are you talking about some sort of stream interface for large files or? |
Yes, for instance downloading tars, or other files of interest. |
I've been giving this some thought and I haven't come up with anything concrete. I wanted to come up with something that wouldn't break the current API but that seems impossible. Option 1: Option 2: Option 3: Option 4: |
I was hoping to work on this issue next week during my company's hackweek. Wanted to get your (@Jason2605 ) thoughts on how you want to see this implemented. Thanks in advance! |
I think option 2 is probably the route I would go with introducing a new bytes type, as this is something that will need doing eventually anyways. Once we have a dedicated bytes type we can default the string type to handle unicode chars to bring the string type into the modern era. Probably the most work involved in this option, but I think it's the way to go! |
Thank you for the feedback! Will get started on this next week. |
Much appreciated, thank you |
I found a workout around for this that will not require any new types or adjustments to the HTTP module. I'll submit the PR by tomorrow night. This will open the door to so much. :D |
Is there an existing issue for this?
Is your feature request related to a problem?
There doesn't appear to be any way of writing the content retrieved from an HTTP call to a file. I don't have any good suggestions on how to implement this as there are a number of ways to examine. Open to suggestions.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: