[Pythonmac-SIG] time and MacPython 2.1a2
Tattoo Mabonzo K.
tmk@easynet.be
Wed, 21 Feb 2001 16:02:16 +0100
--Apple-Mail-616727086-7
content-transfer-encoding: quoted-printable
content-type: text/plain;
charset=us-ascii
Yo,
I've just noticed that on Mac OS X PB, time.time() as well as some =
related time functions (os.path.getmtime()) return *negative* values. =
The doc says that time.time() expected behavior is to=20
"
Return the time as a floating point number expressed in seconds since =
the epoch, in UTC. Note that even though the time is always returned as =
a floating point number, not all systems provide time with a better =
precision than 1 second.
"
time.gmtime(0) returns (1903, 12, 31, 23, 0, 0, 3, 365, 0) which is Thu =
Dec 31, 1903 23:00:00 as the epoch both on Mac OS X PB et on Python 2.0 =
on Mac OS 9.1.=20
I'd expect that time.time() would yield a positive value.=20
On OS XP:
t =3D time.time() -> -1229352415.5447249
time.asctime(time.localtime(t)) -> 'Wed Feb 21 15:41:21 2001'
On Mac OS 9.1 (MacPython 2.0)
t =3D time.time() -> 3065614820.2202692
time.asctime(time.locatime(time.time()) -> 'Wed Feb 21 15:40:20 2001'
=3D tmk =3D
PS: Jack, I'm cc'ing you because I don't see my posts making it to the =
list.=
--Apple-Mail-616727086-7
content-transfer-encoding: quoted-printable
content-type: text/enriched;
charset=us-ascii
<=
flushleft><fontfamily><param>Helvetica</param><x-tabstops><param>28L;56L;8=
4L;112L;140L;168L;196L;224L;252L;280L;308L;336L;</param>Yo,
I've just noticed that on Mac OS X PB, time.time() as well as some =
related time functions (os.path.getmtime()) return *negative* values. =
The doc says that =
time.</x-tabstops></fontfamily><fontfamily><param>Trebuchet =
MS</param><x-tabstops><param>28L;56L;84L;112L;140L;168L;196L;224L;252L;280=
L;308L;336L;</param>time() expected behavior is to=20
"
Return the time as a floating point number expressed in seconds since =
the epoch, in UTC. Note that even though the time is always returned as =
a floating point number, not all systems provide time with a better =
precision than 1 second.
=
"</x-tabstops></fontfamily><fontfamily><param>Helvetica</param><x-tabstops=
><param>28L;56L;84L;112L;140L;168L;196L;224L;252L;280L;308L;336L;</param>
time.gmtime(0) returns (1903, 12, 31, 23, 0, 0, 3, 365, 0) which is Thu =
Dec 31, 1903 23:00:00 as the epoch both on Mac OS X PB et on Python 2.0 =
on Mac OS 9.1.=20
I'd expect that time.time() would yield a positive value.=20
On OS XP:
t =3D time.time() -> -1229352415.5447249
time.asctime(time.localtime(t)) -> 'Wed Feb 21 15:41:21 2001'
On Mac OS 9.1 (MacPython 2.0)
t =3D time.time() -> 3065614820.2202692
time.asctime(time.locatime(time.time()) -> 'Wed Feb 21 15:40:20 2001'
=3D tmk =3D
PS: Jack, I'm cc'ing you because I don't see my posts making it to the =
list.</x-tabstops></fontfamily></flushleft>=
--Apple-Mail-616727086-7--