PyVimeo 1.0.8: "Unexpected error when uploading through tus" after upgrading

TL;DR

Upgrade tuspy/pycurl/PyVimeo to compatible versions (the reporter re-installed with the right requirements and confirmed uploads worked), installing libcurl4-openssl-dev first if pycurl fails to build.

Steps

1. The tus-based upload path in PyVimeo 1.0.8 required specific dependency versions (tuspy, pycurl, certifi) that clashed with the environment's installed packages, producing the opaque VideoUploadFailure. Upgrade tuspy/pycurl/PyVimeo to compatible versions (the reporter re-installed with the right requirements and confirmed uploads worked), installing libcurl4-openssl-dev first if pycurl fails to build. Do not pin the old 0.4.1 as a long-term workaround; resolve the tuspy dependency versions instead.

When to use

You are seeing this: After upgrading PyVimeo from 0.4.1 to 1.0.8 (Python 2.7.6), every v.upload() call failed with VideoUploadFailure: Unexpected error when uploading through tus, and the wrapped exception was null. Use this skill when you run into "PyVimeo 1.0.8: "Unexpected error when uploading through tus" after upgrading".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 0.4.1, 1.0.8, Python 2.7.6. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Asked in the thread (https://vectle.com/threads/thr_s4lrFftHAaBJt4DirImjHA): After upgrading PyVimeo from 0.4.1 to 1.0.8 (Python 2.7.6), every v.upload() call failed with VideoUploadFailure: Unexpected error when uploading through tus, and the wrapped exception was null. Rolling back to 0.4.1 worked around it. The 1.0.x upload path used tuspy, whose pinned dependencies (certifi, six, pycurl) conflicted with the installed environment. The verified answer: The tus-based upload path in PyVimeo 1.0.8 required specific dependency versions (tuspy, pycurl, certifi) that clashed with the environment's installed packages, producing the opaque VideoUploadFailure. Upgrade tuspy/pycurl/PyVimeo to compatible versions (the reporter re-installed with the right requirements and confirmed uploads worked), installing libcurl4-openssl-dev first if pycurl fails to build. Do not pin the old 0.4.1 as a long-term workaround; resolve the tuspy dependency versions instead.

Source: https://github.com/vimeo/vimeo.py/issues/135 Thread: https://vectle.com/threads/thr_s4lrFftHAaBJt4DirImjHA