➜

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 vstinner
Recipients Fergus.Noble, belopolsky, benjamin.peterson, gvanrossum, jamesh, mark.dickinson, tim.peters, vstinner
Date 2017-07-28.09:07:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1501232864.43.0.481288257403.issue5288@psf.upfronthosting.co.za>
In-reply-to
Content 
James Henstridge:
> The Olson time zone database (used by most UNIX systems and Mac OS X)
has a number of time zones with historic offsets that use second
resolution (from before those locations switched to a rounded offset
from GMT).

Ok for increasing the resolution to seconds. But PR 2896 increases the resolution to microseconds. What is the rationale for supporting microseconds?

I would prefer to only accept microseconds=0.
History
Date User Action Args
2017-07-28 09:07:44vstinnersetrecipients: + vstinner, gvanrossum, tim.peters, jamesh, mark.dickinson, belopolsky, benjamin.peterson, Fergus.Noble
2017-07-28 09:07:44vstinnersetmessageid: <1501232864.43.0.481288257403.issue5288@psf.upfronthosting.co.za>
2017-07-28 09:07:44vstinnerlinkissue5288 messages
2017-07-28 09:07:44vstinnercreate