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
Date 2010-06-16.17:58:29
SpamBayes Score 0.002946224
Marked as misclassified No
Message-id <>
This idea was brought in the original fixed offset timezone proposal (see issue 5094), but was met with some opposition.  See msg106914, point 2. As a result, the timezone implementation is in conflict with tzinfo documentation that says "If utcoffset() does not return None, dst() should not return None either."

Note that dst() is not needed for time calculations involving fixed offset timezones because DST shift is included in utcoffset().  It is however needed for interoperability with timetuple time representation. See issue9004.

If the long term goal is to move users from using timetuples to to datetime objects, it is important for time objects to be able to store DST flag.
Date User Action Args
2010-06-16 17:58:31belopolskysetrecipients: + belopolsky
2010-06-16 17:58:31belopolskysetmessageid: <>
2010-06-16 17:58:29belopolskylinkissue9013 messages
2010-06-16 17:58:29belopolskycreate