RetroSearch Browse

Mon Jun 27 03:26:40 CEST 2005 · https://mail.python.org/pipermail/python-dev/2005-June/054457.html

On Jun 26, 2005, at 8:54 PM, Phillip J. Eby wrote:

> At 12:22 AM 6/27/2005 +0200, Dörwald Walter wrote:
>
>> Phillip J. Eby wrote:
>>
>>> [...]
>>> I'm also not keen on the fact that it makes certain things
>>> properties whose value can change over time; i.e. ctime/mtime/atime
>>> and
>>> size really shouldn't be properties, but rather methods.
>>>
>>
>> I think ctime, mtime and atime should be (or return)
>> datetime.datetime objects instead of integer timestamps.
>>
>
> With what timezone?  I don't think that can be done portably and
> unambiguously, so I'm -1 on that.

That makes no sense, timestamps aren't any better, and datetime  
objects have no time zone set by default anyway.   
datetime.fromtimestamp(time.time()) gives you the same thing as  
datetime.now().

-bob

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2005-June/054457.html below:

[Python-Dev] Adding the 'path' module (was Re: Some RFE for review)