This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

作者 belopolsky
收信人 belopolsky, georg.brandl, gvanrossum, nnorwitz, pboddie, pitrou, techtonik
日期 2011-01-11.14:18:00
SpamBayes Score 4.089446e-09
Marked as misclassified
Message-id <AANLkTimMWNqqovHOmDaPrGp6ctq=rKAGZ1xNk7P97uL4@mail.gmail.com>
In-reply-to <1294740390.79.0.768157681082.issue1667546@psf.upfronthosting.co.za>
内容
On Tue, Jan 11, 2011 at 5:06 AM, anatoly techtonik
<report@bugs.python.org> wrote:
..
> IIUC #9527 is about datetime and this request is about time.localtime,

This is correct, but did you notice what I wrote in my last message?

"""
In order to properly implement #9527 in datetime.py, some kind of
tm_gmtoff support will need to be added to the time module, but I
don't want this to become a feature that is exclusively available from
the time module.
"""

I am not rejecting this request, I am trying to consolidate two
closely related issues.  Can you explain why you believe this
functionality should be provided exclusively through the time module
and not be available in datetime?
历史
日期 用户 动作 参数
2011-01-11 14:18:02belopolsky修改recipients: + belopolsky, gvanrossum, nnorwitz, georg.brandl, pboddie, pitrou, techtonik
2011-01-11 14:18:00belopolsky链接issue1667546 messages
2011-01-11 14:18:00belopolsky创建