From 53a9db37a96524ee500230cee5865d81dad93a51 Mon Sep 17 00:00:00 2001 From: Stuart Bishop Date: Fri, 22 Apr 2016 19:57:53 +0700 Subject: Fix old example insisting normalize() is necessary after astimezone() conversion --- src/README.txt | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/src/README.txt b/src/README.txt index 00566ae..064b760 100644 --- a/src/README.txt +++ b/src/README.txt @@ -134,19 +134,21 @@ section for more details) >>> dt2.strftime(fmt) '2002-10-27 01:30:00 EST-0500' -Converting between timezones also needs special attention. We also need -to use the ``normalize()`` method to ensure the conversion is correct. +Converting between timezones is more easily done, using the +standard astimezone method. >>> utc_dt = utc.localize(datetime.utcfromtimestamp(1143408899)) >>> utc_dt.strftime(fmt) '2006-03-26 21:34:59 UTC+0000' >>> au_tz = timezone('Australia/Sydney') ->>> au_dt = au_tz.normalize(utc_dt.astimezone(au_tz)) +>>> au_dt = utc_dt.astimezone(au_tz) >>> au_dt.strftime(fmt) '2006-03-27 08:34:59 AEDT+1100' ->>> utc_dt2 = utc.normalize(au_dt.astimezone(utc)) +>>> utc_dt2 = au_dt.astimezone(utc) >>> utc_dt2.strftime(fmt) '2006-03-26 21:34:59 UTC+0000' +>>> utc_dt == utc_dt2 +True You can take shortcuts when dealing with the UTC side of timezone conversions. ``normalize()`` and ``localize()`` are not really -- cgit v1.2.1