The underlying REST API supports paging, but it is masked in a few places by overly-strict function signatures.
When a function gets called from the AccessMethodsMixin collection, the page=1 keyword argument gets passed along to the REST request. However some of the functions defined in the Eventbrite class (such as get_event_attendees) mask the auto-generated functions and don't have the page keyword argument, so there's no way to get to the second page.
It would also be nice to have a helper utility to automatically retrieve the pages.
The underlying REST API supports paging, but it is masked in a few places by overly-strict function signatures.
When a function gets called from the
AccessMethodsMixincollection, thepage=1keyword argument gets passed along to the REST request. However some of the functions defined in theEventbriteclass (such asget_event_attendees) mask the auto-generated functions and don't have thepagekeyword argument, so there's no way to get to the second page.It would also be nice to have a helper utility to automatically retrieve the pages.