Update to work with latest Python, better implementation of Tus, and more flexible blueprint usage (instead of add_url_rule)

[jzwolak]

I could not use Flask-Tus out of the box with frontend Tus-compatible libraries. I tried Uppy in particular.

I made these modifications to get Flask-Tus working with Uppy... I'd say... it's barely working. But it works.

I also wonder if you'll be deploying Flask-Tus any longer - in order to use with pip install. If not, I'd really like to deploy my changes and continue more work on the project.

[gnubyte]

I too have an interest in this. Opened #5 where we can discuss plans to move forward with maintaining this software.

[jzwolak]

Hi Gareth, yes, please use the changes I made. I put them on Github so that others wouldn’t have to struggle with what I struggled with. I also hoped to form some connections where we might support each other on this project.

We are using exactly what I put on Github in production for a year now without problems. Though it is a lightly used project.

I do ask that you let me know how it goes and if it works for you. I would very much like to know what your experience is with flask-tus and the changes I made! I really did the bare minimum to get things working, so expect to do some more work unless your use case is identical to mine.

-- Jason Zwolak On Oct 29, 2020, 6:23 PM -0400, Gareth Leake [email protected], wrote:

@gnubyte I also have an interest in using this. My team at Mediaocean is interested in using this together with Uppy. @jzwolak -- would it be alright with you if I copied over your changes? I'm guessing this isn't actively maintained, so idk if it will get merged. cc @cartfisk — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.