Module pagers (1.10.0)

Version 1.10.0

• 1.23.0 (latest)
• 1.22.0
• 1.21.2
• 1.20.1
• 1.19.1
• 1.18.0
• 1.17.0
• 1.16.3
• 1.15.1
• 1.14.1
• 1.13.0
• 1.12.0
• 1.11.0
• 1.10.2
• 1.9.0
• 1.8.1
• 1.7.0
• 1.6.1
• 1.5.0
• 1.4.1
• 1.3.0
• 1.2.1
• 1.1.0
• 1.0.2
• 0.4.2
• 0.3.1
• 0.2.0
• 0.1.0

API documentation for retail_v2alpha.services.model_service.pagers module.

Classes

ListModelsAsyncPager

ListModelsAsyncPager(
    method: Callable[
        [...],
        Awaitable[google.cloud.retail_v2alpha.types.model_service.ListModelsResponse],
    ],
    request: google.cloud.retail_v2alpha.types.model_service.ListModelsRequest,
    response: google.cloud.retail_v2alpha.types.model_service.ListModelsResponse,
    *,
    metadata: Sequence[Tuple[str, str]] = ()
)

A pager for iterating through list_models requests.

This class thinly wraps an initial ListModelsResponse object, and provides an __aiter__ method to iterate through its models field.

If there are more pages, the __aiter__ method will make additional ListModels requests and continue to iterate through the models field on the corresponding responses.

All the usual ListModelsResponse attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.

ListModelsPager

ListModelsPager(
    method: Callable[
        [...], google.cloud.retail_v2alpha.types.model_service.ListModelsResponse
    ],
    request: google.cloud.retail_v2alpha.types.model_service.ListModelsRequest,
    response: google.cloud.retail_v2alpha.types.model_service.ListModelsResponse,
    *,
    metadata: Sequence[Tuple[str, str]] = ()
)

A pager for iterating through list_models requests.

This class thinly wraps an initial ListModelsResponse object, and provides an __iter__ method to iterate through its models field.

If there are more pages, the __iter__ method will make additional ListModels requests and continue to iterate through the models field on the corresponding responses.

All the usual ListModelsResponse attributes are available on the pager. If multiple requests are made, only the most recent response is retained, and thus used for attribute lookup.