.me.videos() only produces 24 videos

[vimeo]

.me.videos() only produces 24 videos

[sclm]

There actually should be an upper limit here, the fact that you can request 9001 is likely a bug. Pagination is required for our own performance.

The response object has pagination helper methods, so you can use them to get the next, last, first and previous pages. The pagination functions were previously always there, but I patched them so that they won't be set if they're set to null/None (this is in 2795110).

The code that would load all of the pages into a list is below, but bear in mind that this does mean that it's allocating memory for every one and won't be cleaned up. A more ideal way to do this would probably to process the data inside the same while loop and spare yourself that headache.

vc = vimeo.VimeoClient(**client_args)

all_videos = list()

resp = vc.me.videos(per_page=1)
all_videos = resp['body']['data']

while hasattr(resp, 'next') and resp.next:
    resp = resp.next()
    all_videos.extend(resp['body']['data'])

pprint(all_videos)

Sorry this does it one per page, but that's how I can test it since I don't quite have as many videos as you do.

[natfarleydev]

If paging is needed (which it is), then this solution seems good to me. I'll switch over my code to this method soon.

[natfarleydev]

I found that resp always has a next() method, and just loops round when it gets to the end. To solve this I just did

while resp.next()['body']['page'] == resp['body']['page'] + 1:
        resp = resp.next()
        all_my_videos.extend(resp['body']['data'])

for the loop instead.

[sclm]

@nasfarley88 That was the bug that was corrected in my latest commit. We were always creating the helper methods for URIs in the paging object, even when the URI was none. The change performs a test for None (or any false-y value) before binding the method onto the object.