[issue3185] Documentation of time.time() differs from source documentation

2008-06-24 Thread Martin v. Löwis
Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I think you are misinterpreting what you are seeing. time.mktime returns seconds since the Epoch, in UTC, when passed broken-down local time. So that the result is the same as time.time() doesn't mean that time.time() returns "local unix seco

[issue3185] Documentation of time.time() differs from source documentation

2008-06-23 Thread Carsten Grohmann
Carsten Grohmann <[EMAIL PROTECTED]> added the comment: "current local unix seconds" means seconds since the Epoch in local timezone. I've attached a small example to show that is no difference between the time returned by time.localtime() and time.time(). So I assume that time.time() also retur

[issue3185] Documentation of time.time() differs from source documentation

2008-06-23 Thread Martin v. Löwis
Martin v. Löwis <[EMAIL PROTECTED]> added the comment: I cannot see the difference. The docstring doesn't say "current local time", it says "current time". What do you mean by "current local unix seconds" - that phrase makes no sense. time.time() returns the seoncds since the Epoch, and they mus

[issue3185] Documentation of time.time() differs from source documentation

2008-06-23 Thread Carsten Grohmann
New submission from Carsten Grohmann <[EMAIL PROTECTED]>: The current python documentation of the time module (http://docs.python.org/lib/module-time.html) means that time.time() returns the "seconds since the epoch, in UTC". But in the current source documentation of the time module (http://svn