Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Thu, May 5, 2011 at 12:44 PM, R. David Murray <rep...@bugs.python.org> wrote: .. > Do you think we can get 9527 in? I hope we can. Pure Python implementation can be improved by deducing the TZ offset from localtime() and gmtime() calls. In C we can use additional struct tm fields when they are available to do even better. Would you like to add your voice to support #9527? .. > I'll have to keep a flag for the 60th second outside of the datetime > instance (or pretend it doesn't exist :) If you can find an e-mail message archived somewhere with 60 seconds in the timestamp, it will be a powerful argument to extend seconds range that can be stored in datetime objects. I doubt such messages exist, though. Few systems can produce such a timestamp even if they happen to process an e-mail during a leap second. In parse_datetime(), your choice will be between raising an error and approximating the leap second with the nearest representable time. I think clamping 60 seconds to 59 is the best option and this is what datetime.fromtimestamp does if the system happens to produce a leap second in the timetuple. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue665194> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
