PaginatorLink to this heading#

Paginator classLink to this heading#

class Paginator(object_list, per_page, orphans=0, allow_empty_first_page=True)Link to this definition#

A paginator acts like a sequence of Page when using len() or iterating it directly.

Paginator.object_listLink to this definition#

Required. A list, tuple, QuerySet, or other sliceable object with a count() or __len__() method. For consistent pagination, QuerySets should be ordered, e.g. with an order_by() clause or with a default ordering on the model.

Paginator.per_pageLink to this definition#

Required. The maximum number of items to include on a page, not including orphans (see the orphans optional argument below).

Paginator.orphansLink to this definition#

Optional. Use this when you don't want to have a last page with very few items. If the last page would normally have a number of items less than or equal to orphans, then those items will be added to the previous page (which becomes the last page) instead of leaving the items on a page by themselves. For example, with 23 items, per_page=10, and orphans=3, there will be two pages; the first page with 10 items and the second (and last) page with 13 items. orphans defaults to zero, which means pages are never combined and the last page may have one item.

Paginator.allow_empty_first_pageLink to this definition#

Optional. Whether or not the first page is allowed to be empty. If False and object_list is empty, then an EmptyPage error will be raised.

Page classLink to this heading#

You usually won't construct Page objects by hand -- you'll get them by iterating Paginator, or by using Paginator.page().

class Page(object_list, number, paginator)Link to this definition#

1つのページは、len() を使ったり直接イテレーションした時、Page.object_list のシーケンスのように振る舞います。

例外Link to this heading#

exception InvalidPageLink to this definition#

pagenator に無効なページ数が渡された時に発生する例外のベースクラスです。

The Paginator.page() method raises an exception if the requested page is invalid (i.e. not an integer) or contains no objects. Generally, it's enough to catch the InvalidPage exception, but if you'd like more granularity, you can catch either of the following exceptions:

exception PageNotAnIntegerLink to this definition#

Raised when page() is given a value that isn't an integer.

exception EmptyPageLink to this definition#

Raised when page() is given a valid value but no objects exist on that page.

Both of the exceptions are subclasses of InvalidPage, so you can handle them both with except InvalidPage.