This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author belopolsky
Recipients belopolsky, georg.brandl, lemburg, loewis, luckmor
Date 2010-06-26.01:25:43
SpamBayes Score 0.00090175547
Marked as misclassified No
Message-id <1277515545.93.0.783956984459.issue4775@psf.upfronthosting.co.za>
In-reply-to
Content
Python implementation of time functions certainly has nothing to do with UT1, which is the time as measured by (modern) sun dials.  The correct name would be POSIX time.  As explained in POSIX rationale,

"""
Coordinated Universal Time (UTC) includes leap seconds. However, in POSIX time (seconds since the Epoch), leap seconds are ignored (not applied) to provide an easy and compatible method of computing time differences. Broken-down POSIX time is therefore not necessarily UTC, despite its appearance.
""" -- http://www.opengroup.org/onlinepubs/9699919799/xrat/V4_xbd_chap04.html

Nevertheless, UTC time is used throughout the standard.  For example,

"""
The gmtime() function shall convert the time in seconds since the Epoch pointed to by timer into a broken-down time, expressed as Coordinated Universal Time (UTC).
""" -- http://www.opengroup.org/onlinepubs/9699919799/functions/gmtime.html


I don't think there is much that can be improved in the Python documentation other than to stop referring to UTC as if it was a geographical location.
History
Date User Action Args
2010-06-26 01:25:46belopolskysetrecipients: + belopolsky, lemburg, loewis, georg.brandl, luckmor
2010-06-26 01:25:45belopolskysetmessageid: <1277515545.93.0.783956984459.issue4775@psf.upfronthosting.co.za>
2010-06-26 01:25:44belopolskylinkissue4775 messages
2010-06-26 01:25:43belopolskycreate