> >> I am not the maintainer of the datetime module, but based purely on what
> >> you have said, I would consider that a bug.
>
> I don't. Do you really want every time function slowed by
> re-initializing the timezone?
It depends; do you know what re-initializing entails and how costly
that wo
On 4/3/2013 2:46 PM, CM wrote:
On Apr 3, 7:37 am, Steven D'Aprano wrote:
On Tue, 02 Apr 2013 17:04:12 -0700, CM wrote:
To summarize the issue: In an application, I have been using Python's
datetime module to get the current time. But it seems that, at least
with Windows (XP), whatever time z
On Apr 3, 7:37 am, Steven D'Aprano wrote:
> On Tue, 02 Apr 2013 17:04:12 -0700, CM wrote:
> > To summarize the issue: In an application, I have been using Python's
> > datetime module to get the current time. But it seems that, at least
> > with Windows (XP), whatever time zone your computer is
> 2013-04-03 14:41:13.124000 < WRONG
> ^
(That carrot is supposed to be pointing to the 4 in 14, which should
be 18.)
--
http://mail.python.org/mailman/listinfo/python-list
On Tue, 02 Apr 2013 17:04:12 -0700, CM wrote:
> To summarize the issue: In an application, I have been using Python's
> datetime module to get the current time. But it seems that, at least
> with Windows (XP), whatever time zone your computer is set to when you
> start the application, that's wh
Although there is an answer to my concern posted on Stack Overflow[1],
I thought I'd run this by the Python group to just get a read on it,
since it strikes me as a concern.
To summarize the issue: In an application, I have been using Python's
datetime module to get the current time. But it seem
