Emphasising "time object" in documentation
|Reported by:||Kristian Glass||Owned by:||nobody|
|Cc:||Triage Stage:||Ready for checkin|
|Has patch:||yes||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
"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 Changed 3 years ago by
|Triage Stage:||Unreviewed → Ready for checkin|
|Type:||Uncategorized → Cleanup/optimization|