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 Fergus.Noble, belopolsky, benjamin.peterson, gvanrossum, jamesh, mark.dickinson, tim.peters, vstinner
Date 2017-07-28.14:40:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

Tim called for removal of all restrictions on the offsets.  See msg248468.  I left the range restriction intact because we have some algorithms that rely on that, but in general I agree with Tim.  There is nothing to be gained from restricting the offsets.  It is just some extra code to enforce gratuitous limitations.

Note that Olson's database limits its precision to seconds for historical reasons.  The mean solar time offsets that they record are known to subsecond precision.

I did add a few lines of code to support subsecond formatting, but at some point we should be able to unify timedelta and timezone formatting.
Date User Action Args
2017-07-28 14:40:36belopolskysetrecipients: + belopolsky, gvanrossum, tim.peters, jamesh, mark.dickinson, vstinner, benjamin.peterson, Fergus.Noble
2017-07-28 14:40:36belopolskysetmessageid: <>
2017-07-28 14:40:36belopolskylinkissue5288 messages
2017-07-28 14:40:36belopolskycreate