On Tue, Jun 17, 2008 at 11:09 AM, Curt Hagenlocher <curt at hagenlocher.org> wrote: > On Tue, Jun 17, 2008 at 10:56 AM, Guido van Rossum <guido at python.org> wrote: >> On Tue, Jun 17, 2008 at 10:40 AM, Curt Hagenlocher <curt at hagenlocher.org> wrote: >>> >>> 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 >>> written as a 32-bit value. >> >> Why is that? Is it because your epoch is different? If so, I would >> much prefer the epoch to be 1970. (Maybe this is the resolution you're >> seeking?) > > Yes! Except that I was hoping for something a little stronger, like > "the epoch must be 1970" or "the epoch can be anything you want, but > you're utterly retarded if you pick something other than 1970". But > I'll definitely settle for "much prefer". :) I could go with the "utterly retarded" wording. :-) -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4