From 4b58e94f271790675782f617288d915169e99654 Mon Sep 17 00:00:00 2001
From: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Sat, 19 May 2012 23:31:38 +0200
Subject: [PATCH] Followed a best practice in the time zones docs.
Prevented localize from swallowing non existent or ambiguous
datetimes.
---
docs/topics/i18n/timezones.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/topics/i18n/timezones.txt b/docs/topics/i18n/timezones.txt
index 89d5ef217e..1d9dd4b3c6 100644
--- a/docs/topics/i18n/timezones.txt
+++ b/docs/topics/i18n/timezones.txt
@@ -656,7 +656,7 @@ Usage
>>> from django.utils.dateparse import parse_datetime
>>> naive = parse_datetime("2012-02-21 10:28:45")
>>> import pytz
- >>> pytz.timezone("Europe/Helsinki").localize(naive)
+ >>> pytz.timezone("Europe/Helsinki").localize(naive, is_dst=None)
datetime.datetime(2012, 2, 21, 10, 28, 45, tzinfo=<DstTzInfo 'Europe/Helsinki' EET+2:00:00 STD>)
Note that ``localize`` is a pytz extension to the :class:`~datetime.tzinfo`