Django

Code

Ticket #2433 (closed: fixed)

Opened 2 years ago

Last modified 2 years ago

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

Reported by: Pete Crosier Assigned to: jacob
Milestone: Component: Generic views
Version: SVN Keywords:
Cc: pete.crosier@gmail.com Triage Stage: Unreviewed
Has patch: 1 Needs documentation: 0
Needs tests: 0 Patch needs improvement: 0

Description

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

date_based.py.diff (7.4 kB) - added by Pete Crosier on 07/26/06 16:33:22.

Change History

07/26/06 16:33:22 changed by Pete Crosier

  • attachment date_based.py.diff added.

07/26/06 16:34:08 changed by anonymous

  • type changed from defect to enhancement.

07/26/06 20:24:04 changed by ubernostrum

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.

07/27/06 11:36:02 changed by adrian

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

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

Add/Change #2433 ([patch]Adds allow_future for date-based generic views.)




Change Properties
Action