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.

Author belopolsky
Recipients belopolsky, docs@python, georg.brandl, napik, techtonik
Date 2011-01-11.16:39:48
SpamBayes Score 2.80731e-12
Marked as misclassified No
Message-id <>
In-reply-to <>
On Tue, Jan 11, 2011 at 11:20 AM, Tomas Kubes <> wrote:
> You should try to think like a person that does not have any background knowledge of underlying libraries but
> just looks through the time library trying to solve the question - how can I check if my machine uses daylight
> savings now.

I think you are confusing the purposes of a reference manual with that
of a tutorial or an FAQ collection.

I will keep this issue open, however, in case someone will come up
with a patch that does not introduce factual mistakes.   As I
suggested, the place to present details about tzname, timezone,
altzone and daylight variables is the section on time.tzset().  It is
currently devoted to a rather useless discussion of the TZ environment
variable syntax.  Instead, it should describe these variables and list
the functions whose behavior depends on the value of TZ
(time.localtime(), time.ctime(), time.mktime() and time.strftime()).
Date User Action Args
2011-01-11 16:39:50belopolskysetrecipients: + belopolsky, georg.brandl, techtonik, napik, docs@python
2011-01-11 16:39:48belopolskylinkissue7229 messages
2011-01-11 16:39:48belopolskycreate