Re: [Python-Dev] Epoch and Platform

2008-06-18 Thread Pete Forman
"Guido van Rossum" <[EMAIL PROTECTED]> writes: > Leap seconds? Leap seconds aren't supposed to exist when looking > at POSIX timestamps. They don't exist when I look at my watch > either, and that's what I expect from any time-keeping device > except those for use by astronomers. That's pre

Re: [Python-Dev] Epoch and Platform

2008-06-18 Thread Guido van Rossum
Leap seconds? Leap seconds aren't supposed to exist when looking at POSIX timestamps. They don't exist when I look at my watch either, and that's what I expect from any time-keeping device except those for use by astronomers. On Wed, Jun 18, 2008 at 2:50 AM, Pete Forman <[EMAIL PROTECTED]> wrote:

Re: [Python-Dev] Epoch and Platform

2008-06-18 Thread Pete Forman
"Guido van Rossum" <[EMAIL PROTECTED]> writes: > On Tue, Jun 17, 2008 at 11:09 AM, Curt Hagenlocher > <[EMAIL PROTECTED]> wrote: >> On Tue, Jun 17, 2008 at 10:56 AM, Guido van Rossum >> <[EMAIL PROTECTED]> wrote: >>> On Tue, Jun 17, 2008 at 10:40 AM, Curt Hagenlocher >>> <[EMAIL PROTECTED]> wrote

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Guido van Rossum
On Tue, Jun 17, 2008 at 11:09 AM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: > On Tue, Jun 17, 2008 at 10:56 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: >> On Tue, Jun 17, 2008 at 10:40 AM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: >>> >>> There's no real urgency. The reason this came up is

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Curt Hagenlocher
On Tue, Jun 17, 2008 at 10:56 AM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > On Tue, Jun 17, 2008 at 10:40 AM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: >> >> There's no real urgency. The reason this came up is because I just >> implemented zlib, which automatically enabled the gzip unit test

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Guido van Rossum
On Tue, Jun 17, 2008 at 10:40 AM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: > I don't *feel* anxious, but my doctor *has* been trying to persuade me > to switch to decaf... > > There's no real urgency. The reason this came up is because I just > implemented zlib, which automatically enabled the

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Curt Hagenlocher
I don't *feel* anxious, but my doctor *has* been trying to persuade me to switch to decaf... There's no real urgency. The reason this came up is because I just implemented zlib, which automatically enabled the gzip unit tests. The gzip tests are failing because the current timestamp can't be writ

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Forest
ISTR using a Microsoft C compiler in the early/mid 1990s whose runtime library used an unusual epoch. I don't recall any others straying from the Unix way, but then again, I haven't been looking for such quirks. Guido wrote: > > ISTR that we force the epoch to be 1970 on all major platforms -- or

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Daniel Stutzbach
On Mon, Jun 16, 2008 at 6:38 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > ISTR that we force the epoch to be 1970 on all major platforms -- or > perhaps it happens to be 1970 even on Windows when using MS's C > runtime. I can confirm that Python under Windows does indeed use the Unix epoch:

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Guido van Rossum
Can you explain why you are so anxious to get this resolved (apart from the beer :-) ? On Tue, Jun 17, 2008 at 9:26 AM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: > Any chance of an Official Pronouncement on this topic? It would help > us greatly -- even if only to figure out who'll be paying fo

Re: [Python-Dev] Epoch and Platform

2008-06-17 Thread Curt Hagenlocher
Any chance of an Official Pronouncement on this topic? It would help us greatly -- even if only to figure out who'll be paying for the next round of beer. On Mon, Jun 16, 2008 at 4:38 PM, Guido van Rossum <[EMAIL PROTECTED]> wrote: > ISTR that we force the epoch to be 1970 on all major platforms

Re: [Python-Dev] Epoch and Platform

2008-06-16 Thread Curt Hagenlocher
>From what I remember, the Microsoft CLIB has been consistent with the Unix epoch since the bad old days of 16-bit. I believe that the Macintosh CLIB used to be based on January 1, 1904 -- but it's been a long time since I did any Mac development and I'm sure it would have changed with OS X. On M

Re: [Python-Dev] Epoch and Platform

2008-06-16 Thread Guido van Rossum
ISTR that we force the epoch to be 1970 on all major platforms -- or perhaps it happens to be 1970 even on Windows when using MS's C runtime. On Mon, Jun 16, 2008 at 4:08 PM, Curt Hagenlocher <[EMAIL PROTECTED]> wrote: > The documentation for the time module says that "the epoch is the point > whe

[Python-Dev] Epoch and Platform

2008-06-16 Thread Curt Hagenlocher
The documentation for the time module says that "the epoch is the point where the time starts. On January 1st of that year, at 0 hours, the ``time since the epoch'' is zero. For Unix, the epoch is 1970. To find out what the epoch is, look at gmtime(0)." This confirms that the epoch is platform-spe