tweaking the upload methods to accept BytesIO

[kjurel]

My workflow forces me to stream files from the internet to BytesIO then modify them a bit (using PIL and MoviePy) then upload them.

But as things currently stand, I have to first save the files to local storage then pass that path to the upload methods' path argument. This is not ideal if I'm deploying my app to a remote machine. I wouldn't have to do this if the methods readily accepted BytesIO type.

I tried looking into the project myself, seems like changing some assert statements and with blocks in the respective rupload methods will do the trick (I couldn't find a way to change the same for thumbnail parameter?).

Is this worth submitting a pull request? I don't exactly know since its highly workflow dependent.
If you could suggest any better solution for my use case, that'd be great.
Thanks for your time.

[EverythingSuckz]

@adw0rd any thoughts?

[adw0rd]

@EverythingSuckz no

Can you send examples of methods for which you would like to implement BytesIO?

If you want to offer something, then send your PR

[kjurel]

@adw0rd and @EverythingSuckz , the more I look into making a PR the more it seems like accepting BytesIO or other python-objects ( PIL.Image.Image and mp.VideoFile ) inside upload methods ( photo_upload or video_upload ) will not solve anything ... sorry ...

only using paths inside those upload methods is critical in the functioning of the library, at least for the video upload parts ( analyze_video ) and there isn't really much advantage to using buffers in image upload methods.

I recommend users write their own cleanup scripts after the file has been uploaded... thank you for your time