#23342: Emphasising "time object" in documentation
---------------------------------+--------------------
Reporter: doismellburning | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 1 | UI/UX: 1
---------------------------------+--------------------
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"
--
Ticket URL: <https://code.djangoproject.com/ticket/23342>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/058.2f27bd14bcdc74fd496c1623238453c4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
