Opened 14 years ago

Closed 14 years ago

#2433 closed enhancement (fixed)

[patch]Adds allow_future for date-based generic views.

Reported by: Pete Crosier Owned by: Jacob
Component: Generic views Version: master
Severity: minor Keywords:
Cc: pete.crosier@… Triage Stage: Unreviewed
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


As discussed on the dev. list, a patch is attached that implements an optional allow_future parameter for all the date-based generic views. The value of this new parameter defaults to False, so as not to make old code start acting strange. It also makes sure next/previous_month and next/previous_day behave as expected (as defined by the current documentation).

Attachments (1) (7.4 KB) - added by Pete Crosier 14 years ago.

Download all attachments as: .zip

Change History (4)

Changed 14 years ago by Pete Crosier

Attachment: added

comment:1 Changed 14 years ago by anonymous

Type: defectenhancement

comment:2 Changed 14 years ago by James Bennett

If no-one has any objections, I'm going to close #608 in favor of this; it also had a patch, but that was against an extremely out-of-date version of Django.

comment:3 Changed 14 years ago by Adrian Holovaty

Resolution: fixed
Status: newclosed

(In [3457]) Fixed #2433 -- Added allow_future option to date-based generic views

Note: See TracTickets for help on using tickets.
Back to Top