Opened 16 years ago
Closed 16 years ago
#7781 closed (fixed)
Paginator missing documentation
Reported by: | hiukkanen | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | pagination | |
Cc: | joni.lahtinen@… | Triage Stage: | Unreviewed |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Paginator or obj_page doesn't include results_per_page.
Change History (7)
comment:1 by , 16 years ago
milestone: | 1.0 |
---|
comment:2 by , 16 years ago
comment:4 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Is Paginator.per_page
what you're looking for?
comment:5 by , 16 years ago
Im not very familiar with python, but if that per_page is an attribute should it be documented here: http://www.djangoproject.com/documentation/pagination/
Thanks for your reply.
comment:6 by , 16 years ago
Component: | Template system → Documentation |
---|---|
Resolution: | invalid |
Status: | closed → reopened |
Summary: | Django development version limits information in pagination → Paginator missing documentation |
As noted by hiukkanen, the replacement for ObjectPaginator's num_per_page is not documented. Makes it appear from reading the doc that there is no replacement for an old ObjectPaginator function, causing great distress now that ObjectPagintor is Gone. (Well, maybe more minor annoyance than great distress...)
comment:7 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
obj_page = page_obj
page_obj.object_list|len is not always the same as results_per_page (last page).