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 napik
Recipients georg.brandl, napik
Date 2009-10-28.09:44:09
SpamBayes Score 2.3922476e-06
Marked as misclassified No
Message-id <1256723052.19.0.148648938954.issue7229@psf.upfronthosting.co.za>
In-reply-to
Content
Hello,

it is not obvious that the time.daylight data item reports nonzero
values even when DST is currently not being used (ie. in winter) but the
active timezone has DST defined for some other parts of the year.

Current manual entry can be misleadingly interpreted that time.daylight
acts as a current DST idicator (which it does not).

Suggested FIX: Add a sentence:
This value does not idicate that DST is currently active, but rather
describes that current timezone can have DST. Use localtime() dst flag
to determine if DST applies to the given time.


Tomas
History
Date User Action Args
2009-10-28 09:44:12napiksetrecipients: + napik, georg.brandl
2009-10-28 09:44:12napiksetmessageid: <1256723052.19.0.148648938954.issue7229@psf.upfronthosting.co.za>
2009-10-28 09:44:10napiklinkissue7229 messages
2009-10-28 09:44:09napikcreate