Daniel O'Connor added the comment:
On 17/08/2011, at 10:30, Alexander Belopolsky wrote:
> Alexander Belopolsky added the comment:
>
>> i.e. it appears that replace() applies the TZ offset to a naive datetime
>> object effectively assuming it is local time rather than un-timezoned
>> (which is
Alexander Belopolsky added the comment:
> i.e. it appears that replace() applies the TZ offset to a naive datetime
> object effectively assuming it is local time rather than un-timezoned
> (which is what the docs imply to me)
I don't understand your issue. The replace method does not assume an
R. David Murray added the comment:
OK. At a minimum there is a doc issue here, so I'm reopening.
--
nosy: +belopolsky
resolution: invalid ->
status: closed -> open
title: datetime.datetime timezone problems -> datetime.datetime how to
correctly attach a timezone to an existing naive d
