Django provides a few classes that help you manage paginated data – that is,\ndata that’s split across several pages, with „Previous/Next” links. These\nclasses live in django/core/paginator.py.
Give Paginator a list of objects, plus the number of items you’d like to\nhave on each page, and it gives you methods for accessing the items for each\npage:
>>> from django.core.paginator import Paginator\n>>> objects = ['john', 'paul', 'george', 'ringo']\n>>> p = Paginator(objects, 2)\n\n>>> p.count\n4\n>>> p.num_pages\n2\n>>> type(p.page_range)\n<class 'range_iterator'>\n>>> p.page_range\nrange(1, 3)\n\n>>> page1 = p.page(1)\n>>> page1\n<Page 1 of 2>\n>>> page1.object_list\n['john', 'paul']\n\n>>> page2 = p.page(2)\n>>> page2.object_list\n['george', 'ringo']\n>>> page2.has_next()\nFalse\n>>> page2.has_previous()\nTrue\n>>> page2.has_other_pages()\nTrue\n>>> page2.next_page_number()\nTraceback (most recent call last):\n...\nEmptyPage: That page contains no results\n>>> page2.previous_page_number()\n1\n>>> page2.start_index() # The 1-based index of the first item on this page\n3\n>>> page2.end_index() # The 1-based index of the last item on this page\n4\n\n>>> p.page(0)\nTraceback (most recent call last):\n...\nEmptyPage: That page number is less than 1\n>>> p.page(3)\nTraceback (most recent call last):\n...\nEmptyPage: That page contains no results\nPaginator in a viewLink to this heading#Here’s a slightly more complex example using Paginator in a view to\npaginate a queryset. We give both the view and the accompanying template to\nshow how you can display the results. This example assumes you have a\nContacts model that has already been imported.
The view function looks like this:
\nfrom django.core.paginator import Paginator\nfrom django.shortcuts import render\n\ndef listing(request):\n contact_list = Contacts.objects.all()\n paginator = Paginator(contact_list, 25) # Show 25 contacts per page\n\n page = request.GET.get('page')\n contacts = paginator.get_page(page)\n return render(request, 'list.html', {'contacts': contacts})\nIn the template list.html, you’ll want to include navigation between\npages along with any interesting information from the objects themselves:
{% for contact in contacts %}\n {# Each "contact" is a Contact model object. #}\n {{ contact.full_name|upper }}<br>\n ...\n{% endfor %}\n\n<div class="pagination">\n <span class="step-links">\n {% if contacts.has_previous %}\n <a href="?page=1">« first</a>\n <a href="?page={{ contacts.previous_page_number }}">previous</a>\n {% endif %}\n\n <span class="current">\n Page {{ contacts.number }} of {{ contacts.paginator.num_pages }}.\n </span>\n\n {% if contacts.has_next %}\n <a href="?page={{ contacts.next_page_number }}">next</a>\n <a href="?page={{ contacts.paginator.num_pages }}">last »</a>\n {% endif %}\n </span>\n</div>\nPaginator objectsLink to this heading#The Paginator class has this constructor:
object_listA list, tuple, QuerySet, or other sliceable object with a count()\nor __len__() method. For consistent pagination, QuerySets should\nbe ordered, e.g. with an order_by()\nclause or with a default ordering on the\nmodel.
per_pageThe maximum number of items to include on a page, not including orphans\n(see the orphans optional argument below).
orphansUse this when you don’t want to have a last page with very few items.\nIf the last page would normally have a number of items less than or equal\nto orphans, then those items will be added to the previous page (which\nbecomes the last page) instead of leaving the items on a page by\nthemselves. For example, with 23 items, per_page=10, and\norphans=3, there will be two pages; the first page with 10 items and\nthe second (and last) page with 13 items. orphans defaults to zero,\nwhich means pages are never combined and the last page may have one item.
allow_empty_first_pageWhether or not the first page is allowed to be empty. If False and\nobject_list is empty, then an EmptyPage error will be raised.
Returns a Page object with the given 1-based index, while also\nhandling out of range and invalid page numbers.
If the page isn’t a number, it returns the first page. If the page number\nis negative or greater than the number of pages, it returns the last page.
\nIt raises an exception (EmptyPage) only if you specify\nPaginator(..., allow_empty_first_page=False) and the object_list is\nempty.
Returns a Page object with the given 1-based index. Raises\nInvalidPage if the given page number doesn’t exist.
Całkowita liczba obiektów na wszystkich stronach.
\n\nCałkowita liczba stron
\nA 1-based range iterator of page numbers, e.g. yielding [1, 2, 3, 4].
InvalidPage exceptionsLink to this heading#A base class for exceptions raised when a paginator is passed an invalid\npage number.
\nThe Paginator.page() method raises an exception if the requested page is\ninvalid (i.e., not an integer) or contains no objects. Generally, it’s enough\nto catch the InvalidPage exception, but if you’d like more granularity,\nyou can catch either of the following exceptions:
Raised when page() is given a value that isn’t an integer.
Raised when page() is given a valid value but no objects exist on that\npage.
Both of the exceptions are subclasses of InvalidPage, so you can handle\nthem both with a simple except InvalidPage.
Page objectsLink to this heading#You usually won’t construct Page objects by hand – you’ll get them\nusing Paginator.page().
A page acts like a sequence of Page.object_list when using\nlen() or iterating it directly.
Returns True if there’s a next page.
Returns True if there’s a previous page.
Returns True if there’s a next or previous page.
Returns the next page number. Raises InvalidPage if next page\ndoesn’t exist.
Returns the previous page number. Raises InvalidPage if previous\npage doesn’t exist.
Returns the 1-based index of the first object on the page, relative to all\nof the objects in the paginator’s list. For example, when paginating a list\nof 5 objects with 2 objects per page, the second page’s\nstart_index() would return 3.
Returns the 1-based index of the last object on the page, relative to all\nof the objects in the paginator’s list. For example, when paginating a list\nof 5 objects with 2 objects per page, the second page’s\nend_index() would return 4.
The list of objects on this page.
\nThe 1-based page number for this page.
\nThe associated Paginator object.