Opened 18 years ago
Closed 18 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: | dev |
| 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 |
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 (1)
Change History (4)
by , 18 years ago
| Attachment: | date_based.py.diff added |
|---|
comment:1 by , 18 years ago
| Type: | defect → enhancement |
|---|
comment:2 by , 18 years ago
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
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.