#9853 closed (fixed)
DateField and DateTimeField documentation incomplete
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.0 |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | UI/UX: |
Description
The documentation in the Model Field Reference for the DateField, DateTimeField and TimeField does not mention that these fields normalize to python datetime objects. The documention also does not indicate how to set or modify these values in python code (although acceptable inputs in forms is documented in the Form Fields reference).
I think the DateField doc (http://docs.djangoproject.com/en/dev/ref/models/fields/#datefield) could be improved as follows:
Current: A date field. Has a few extra optional arguments:
Suggested: A date field. Normalizes to a python datetime.date object. Has a few optional arguments.
And similarly for DateTimeField and TimeField.
Attachments (1)
Change History (6)
comment:1 Changed 9 years ago by
| milestone: | → 1.1 |
|---|---|
| Triage Stage: | Unreviewed → Accepted |
Changed 9 years ago by
| Attachment: | field_normalization.diff added |
|---|
comment:2 Changed 9 years ago by
| Has patch: | set |
|---|---|
| Triage Stage: | Accepted → Ready for checkin |
comment:3 Changed 9 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:4 Changed 9 years ago by
Note: See
TracTickets for help on using
tickets.
added notes about normalizing to Python objects