Django

Code

Ticket #1857 (closed: fixed)

Opened 3 years ago

Last modified 2 years ago

[patch] get_next_by_FIELD and get_previous_by_FIELD don't take params

Reported by: tom@jerakeen.org Assigned to: adrian
Milestone: Component: Core framework
Version: Keywords:
Cc: Triage Stage: Unreviewed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

The docs for get_next/previous_by_FIELD state 

Both methods accept optional keyword arguments, which should be in the format described in Field lookups above.

It's not clear what should will do, and anyway, they don't take keyword arguments. This patch makes the method do what I'd expect, which is to return the next/previous page that matches the passed filter params.

Attachments

get_next_previous.diff (1.6 kB) - added by tom@jerakeen.org on 05/14/06 14:15:02.

Change History

05/14/06 14:15:02 changed by tom@jerakeen.org

  • attachment get_next_previous.diff added.

06/19/06 21:17:15 changed by mtredinnick

  • status changed from new to closed.
  • resolution set to fixed.

(In [3157]) Fixed #1857 -- Fixed get_previous_by_FIELD and get_next_by_FIELD to work properly with keyword arguments. Patch from tom@jerakeen.org.

Add/Change #1857 ([patch] get_next_by_FIELD and get_previous_by_FIELD don't take params)




Change Properties
Action