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, jamesh
Date 2010-05-24.16:46:34
SpamBayes Score 0.0024257966
Marked as misclassified No
Message-id <>
As far as I can tell, the TZ offset code can be simplified by eliminating conversion from timedelta to int and back in utcoffset() and dst() methods of time and datetime objects.

The only reason for the restriction that I can think of is that some text representation of datetime only provide 4 digits for timezone. The behavior of formatting functions, can be preserved while allowing fractional minute offsets elsewhere.

On the other hand, given that this issue did not see a single response in more than a year, it seems that there is little interest in fixing it.
Date User Action Args
2010-05-24 16:46:36belopolskysetrecipients: + belopolsky, jamesh
2010-05-24 16:46:35belopolskysetmessageid: <>
2010-05-24 16:46:34belopolskylinkissue5288 messages
2010-05-24 16:46:34belopolskycreate