[Python-checkins] python/nondist/sandbox/datetime US.py,1.7,1.8

2002年12月26日 22:36:55 -0800

Update of /cvsroot/python/python/nondist/sandbox/datetime
In directory sc8-pr-cvs1:/tmp/cvs-serv17500
Modified Files:
	US.py 
Log Message:
Repaired silly repeated cut'n'paste error in comments.
Index: US.py
===================================================================
RCS file: /cvsroot/python/python/nondist/sandbox/datetime/US.py,v
retrieving revision 1.7
retrieving revision 1.8
diff -C2 -d -r1.7 -r1.8
*** US.py	27 Dec 2002 00:13:55 -0000	1.7
--- US.py	27 Dec 2002 06:36:52 -0000	1.8
***************
*** 21,31 ****
 # standard 1am 2am ...
 #
! # There isn't a good solution to deciding what 1:MM:HH means then. If
 # you say it's DST, then there's no way to spell a time in the 1-hour
! # span starting when DST ends: 1:HH:MM would be taken as DST, 2:HH:MM
 # as standard, and in UTC there's a one-hour gap between 1:59:59 DST
 # and 2:00:00 standard. The UTC times in that gap can't be named.
 #
! # OTOH, if you say 1:MM:HH is standard time then, there's no way to
 # spell the hour preceding 1:00:00:. 12:59:59 must be taken as DST,
 # and by hypothesis 1:00:00 is taken as standard, and again there's a
--- 21,31 ----
 # standard 1am 2am ...
 #
! # There isn't a good solution to deciding what 1:MM:SS means then. If
 # you say it's DST, then there's no way to spell a time in the 1-hour
! # span starting when DST ends: 1:MM:SS would be taken as DST, 2:MM:SS
 # as standard, and in UTC there's a one-hour gap between 1:59:59 DST
 # and 2:00:00 standard. The UTC times in that gap can't be named.
 #
! # OTOH, if you say 1:MM:SS is standard time then, there's no way to
 # spell the hour preceding 1:00:00:. 12:59:59 must be taken as DST,
 # and by hypothesis 1:00:00 is taken as standard, and again there's a
***************
*** 33,37 ****
 #
 # The implementation can't win, so this one arbitrarily decides to call
! # 1:MM:HH DST (I expect that's what most people would expect). A
 # consequence of the "missing hour" (under either choice) is that
 # UTC -> this timezone -> UTC can't always be an identity (some one-hour
--- 33,37 ----
 #
 # The implementation can't win, so this one arbitrarily decides to call
! # 1:MM:SS DST (I expect that's what most people would expect). A
 # consequence of the "missing hour" (under either choice) is that
 # UTC -> this timezone -> UTC can't always be an identity (some one-hour
***************
*** 40,45 ****
 # On the other end, when DST starts at 2am on the first Sunday in April,
 # the naive clock magically jumps from 1:59:59 to 3:00:00. A naive time
! # of 2:HH:MM on that day doesn't make sense. We arbitrarily decide it
! # intends DST then, making it a redundant spelling of 1:HH:MM standard
 # on that day.
 
--- 40,45 ----
 # On the other end, when DST starts at 2am on the first Sunday in April,
 # the naive clock magically jumps from 1:59:59 to 3:00:00. A naive time
! # of 2:MM:SS on that day doesn't make sense. We arbitrarily decide it
! # intends DST then, making it a redundant spelling of 1:MM:SS standard
 # on that day.