Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#23342 closed Cleanup/optimization (fixed)

Emphasising "time object" in documentation

Reported by: Kristian Glass Owned by: nobody
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

From ​https://docs.djangoproject.com/en/1.6/topics/i18n/timezones/#naive-and-aware-datetime-objects

"Django only supports naive time objects and will raise an exception if you attempt to save an aware time object."

It's remarkably easy to boggle at that sentence (as several of us in #django just did) until you realise it says "time object" and not "datetime object"

Change History (5)

comment:2 by Aymeric Augustin, 10 years ago

Triage Stage: Unreviewed → Ready for checkin
Type: Uncategorized → Cleanup/optimization
UI/UX: unset

Yes, that's useful.

comment:3 by Tim Graham <timograham@…>, 10 years ago

Resolution: → fixed
Status: new → closed

In b7336ec17917a5cea92e90ac7d1ede6f4c25fdd3:

Fixed #23342 -- Clarified warning about naive time objects.

Thanks to apollo13 for suggested wording.

comment:4 by Tim Graham <timograham@…>, 10 years ago

In 8aca08f82888ccc0aaf981c04ce7e5bcb4048d88:

[1.7.x] Fixed #23342 -- Clarified warning about naive time objects.

Thanks to apollo13 for suggested wording.

Backport of b7336ec179 from master

comment:5 by Tim Graham <timograham@…>, 10 years ago

In d3c75da7fbcdf5d32ab332c9de276e1ffd15f312:

[1.6.x] Fixed #23342 -- Clarified warning about naive time objects.

Thanks to apollo13 for suggested wording.

Backport of b7336ec179 from master

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