Opened 2 years ago

Closed 2 years ago

Last modified 2 years ago

#23342 closed Cleanup/optimization (fixed)

Emphasising "time object" in documentation

Reported by: Kristian Glass Owned by: nobody
Component: Documentation Version: master
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:1 Changed 2 years ago by Kristian Glass

Needs documentation: unset
Needs tests: unset
Patch needs improvement: unset

comment:2 Changed 2 years ago by Aymeric Augustin

Triage Stage: UnreviewedReady for checkin
Type: UncategorizedCleanup/optimization
UI/UX: unset

Yes, that's useful.

comment:3 Changed 2 years ago by Tim Graham <timograham@…>

Resolution: fixed
Status: newclosed

In b7336ec17917a5cea92e90ac7d1ede6f4c25fdd3:

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

Thanks to apollo13 for suggested wording.

comment:4 Changed 2 years ago by Tim Graham <timograham@…>

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 Changed 2 years ago by Tim Graham <timograham@…>

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