Opened at 2010-06-12T04:06:19Z
Last modified at 2016-01-23T00:44:36Z
#1077 assigned defect
consistent timestamp format and timezone — at Initial Version
| Reported by: | zooko | Owned by: | somebody |
|---|---|---|---|
| Priority: | major | Milestone: | soon |
| Component: | code | Version: | 1.7β |
| Keywords: | time usability logging | Cc: | |
| Launchpad Bug: |
Description
All timestamps which are visible in the user interface, log files or other files, automatically generated filenames, etc., should be in the same format and timezone. For the present, that format should be RFC 3339 format, e.g. 2010-06-12 03:54:00.12345. There is code in time_format.py that will generate this format (if you tell it to use a space char as separator instead of the default underscore char as separator).
For the present, the timezone should be UTC. For added unambiguity, append the char Z to the end of the timestamp to indicate UTC.
I'll open separate tickets to make the formatting and timezone localizable without losing the consistency and unambiguity. This ticket is just about achieving consistency and unambiguity.
