#8407 closed (fixed)
docs: incorrect output shown for Paginator use in interactive session
| Reported by: | arien | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Accepted | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The docs show an session at the Python prompt where a Paginator's page method throws an InvalidPage exception for pages that don't have any objects; the actual exception thrown is an EmptyPage. While EmptyPage descends from InvalidPage, the display is incorrect and may well confuse people.
Attachments (2)
Change History (6)
by , 17 years ago
| Attachment: | pagination-docs.diff added |
|---|
by , 17 years ago
| Attachment: | pagination-docs-r8629.diff added |
|---|
patch updated for documentation refactor
comment:1 by , 17 years ago
| milestone: | → 1.0 |
|---|
comment:2 by , 17 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:3 by , 17 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Fix to use actual output,. Also corects two (unrelated) glitches while we're here.